Mastering Patent Claim Construction with LLMs (4): Filling the Gaps in the Knowledge Base
The Final Stage of Supplementing the Sources
This is now the final stage of supplementing the source materials. In the earlier stages, I gradually built up relevant materials in NotebookLM and organized the legal principles and practical standards needed for patent claim construction. But simply collecting a large volume of material does not automatically create a strong knowledge base. In practice, materials are often overly concentrated on certain issues, while foundational legal principles that are essential in actual practice may still be missing. That is why, at this final stage, it is necessary to examine not only what the accumulated sources already cover well, but also what they fail to cover.
The core objective of this stage is simple. Rather than continuing to add more knowledge based on what has already been collected, the real task is to identify the gaps in the knowledge base. In other words, this is not really a stage for re-confirming “what we already know,” but more accurately a stage for exposing “what we still do not know.”
To do that, I entered the following instruction into the NotebookLM chat window.
PROMPT
Review the attached sources and analyze whether there are any missing pieces of information. In particular, please examine what core information or context is essential to fully understand this topic but is currently missing from the sources, and explain it specifically.
The purpose of this instruction is not summarization or organization. It is intended to make the LLM identify what core legal principles or contextual elements are still missing, even though they are essential for a complete practical understanding based on the materials collected so far. Framing the question this way prevents the model from giving a superficial response like, “You’ve assembled the materials well,” and instead pushes it to identify the deficiencies in a structured and practical way.
Items Identified as Requiring Supplementary Materials
In response to the instruction above, the materials requiring supplementation were organized as follows.
Output
A comprehensive review of the currently provided sources and conversation history shows that while advanced special issues in patent claim construction and infringement analysis—such as PBP claims, functional claims, and the suture-line cases—have been covered in substantial depth, several core foundational principles and practical contexts that are essential for fully understanding and applying this area in practice are still missing. Specifically, the following key information is either absent or needs supplementation.
1. Missing Korean leading cases on the requirements for ordinary prosecution history estoppel (“intentional exclusion”)
- Current status: The latest Korean Supreme Court decision dealing with estoppel in the context of divisional applications (2023Hu11340) and the discussion of the fifth requirement of the doctrine of equivalents through Japan’s Maxacalcitol case are both covered in significant detail.
- Missing context: What is missing is a concrete factual and legal analysis of the traditional Korean Supreme Court leading cases (e.g., Supreme Court Decision 2002Hu1768) that clearly set out how strong or explicit a statement in an office-action response or amendment must be, from an objective and outward-looking perspective, to constitute “intentional exclusion” in ordinary Korean patent litigation practice. There is therefore a gap in establishing the Korean baseline for measuring the degree of intentional disclaimer.
2. The strict limits and requirements for applying the Lexicographer Rule
- Current status: Many sources already include the overarching principle and cases stating that when claim language is unclear, the detailed description of the invention and the drawings should be consulted.
- Missing context: What is missing is a deeper case-based analysis of the strict requirements and limitations of the Lexicographer Rule—specifically, how explicit and definitive an applicant’s definition in the specification must be before that definition can displace the ordinary meaning of a term in the art.
3. Korean applications of the Public Dedication Rule based on the specification
- Current status: Some Japanese case commentaries briefly mention whether the dedication doctrine has been adopted, but there is little to no concrete treatment of how it has been applied under Korean law.
- Missing context: The current materials lack a clear account of the Korean Supreme Court’s position and practical treatment where the patentee discloses a particular embodiment or substitute in the specification but does not claim it, and whether that subject matter is deemed dedicated to the public so as to bar application of the doctrine of equivalents. Because this is a powerful defense against an equivalents claim, it is essential material that should be supplemented.
4. “Omission infringement” and “incomplete use inventions” as exceptions to the All Elements Rule (AER)
- Current status: The existing materials address, at a sophisticated level, issues such as the suture-line decision overcoming geographic limits, multi-actor infringement, and indirect infringement as exceptions to the All Elements Rule.
- Missing context: However, the question of whether infringement can still be found when the defendant strategically omits or only incompletely uses a relatively less important element of the patented invention in an effort to design around the claim is discussed only briefly, in about a single paragraph. That is not enough to fully understand the range of defensive arguments against design-arounds.
5. Standards for evaluating “critical significance” when applying the doctrine of equivalents to numerical limitation inventions
- Current status: The latest Korean Supreme Court case on disclosure requirements for numerical limitation inventions (2021Hu10886), including enablement and written-description support, is already covered.
- Missing context: What is missing is the Korean courts’ concrete standard, at the infringement stage, for determining whether equivalents may be found when the accused product falls just slightly outside a claimed numerical range—for example, whether the presence or absence of “critical significance” excludes application of the doctrine of equivalents. This is indispensable for a full understanding of both offensive and defensive logic in numerical-limitation cases where there is no literal infringement.
Important Practical Insights Gained at This Stage
The result above means more than simply “we need more materials.” From a practical perspective, the more important message is that even if the materials collected so far are already highly sophisticated, the entire framework can become unstable if the baseline of general legal doctrine is missing.
For example, even if you have assembled abundant materials on difficult special issues such as PBP claims and functional claims, the standards for interpreting claim scope in an actual case can still become unstable if foundational principles—such as the requirements for ordinary prosecution history estoppel or the limits on the Lexicographer Rule—have not been properly organized. Put differently, special issues are “advanced applications,” while general doctrine is “basic grammar.” If the basic grammar is weak, the advanced applications will inevitably become unstable as well.
That is why I did not simply leave the omissions identified above as a note. Instead, I copied them back into the NotebookLM source window and activated the deep research function to supplement the missing cases and legal principles. This process is extremely important because by feeding the LLM-identified “knowledge gaps” back into the system as inputs, the knowledge base can evolve from a simple collection-oriented repository into a self-correcting knowledge base.
Now It Is Time to Organize the Knowledge to Be Injected into the Claude Skill
The next stage is to use the supplemented materials to extract and organize only the core knowledge that should be injected for drafting the Claude Skill. This is where many people make a mistake. Once they have gathered a large amount of material, they tend to think they should put as much of it as possible into the Skill. But in practice, the opposite is often true. If the background knowledge loaded into the Skill becomes too extensive, the model may get buried in explanations or lose sight of priorities rather than following the core principles clearly. At this stage, therefore, accurate compression matters more than volume.
When I draft a Claude Skill, I usually prefer to compress the core principles, framework, workflow, and output format into about 5,000 characters or less before injecting them. This point is especially important in practice. The skill guide, SKILL.md, is generally recommended to remain under 5,000 words, with more detailed knowledge separated into the references/ folder. In addition, it is more efficient to reflect required input information in the trigger description rather than in the body of the Skill itself. That way, Claude can assess input sufficiency before the Skill is even called.
How to Ask Questions to Extract the Core Knowledge While All Sources Are Selected
With all sources selected, I enter the following questions one by one into the NotebookLM chat window to organize the background knowledge that will be injected into the Skill. At present, I have 60 sources registered in my notebook.
PROMPT
1. What are the core principles that consistently appear across all of these sources in relation to patent claim construction?
2. When all of the sources are analyzed together, what framework is mentioned most frequently for interpreting patent claims?
3. Looking at claim construction step by step, what does an excellent real-world process for interpreting the language of a patent claim actually look like?
4. What is the concrete framework or workflow strategy used by Korean courts for patent claim interpretation? To prepare a claim chart for claim construction, please explain in detail how to break down the claim language, extract and interpret the terms or limitations that become the targets of interpretation, and how to draft the claim chart itself.
This sequence of questions was not chosen arbitrarily. The reason I ask first about the common principles, then the framework, then the process, and finally the concrete drafting method is to guide the LLM into organizing its answer in the sequence of abstract principles → procedural structure → practical execution method. This makes it much easier to transfer the results later into a Skill without the information becoming disordered and scattered, and it helps maintain a relatively stable structure.
The Final Claude Skill Injection Guide Organized in NotebookLM
The final guide I organized in NotebookLM for injection into the Claude Skill is as follows.
PROMPT
Korean courts, in determining the scope of patent rights in infringement litigation and invalidation proceedings, apply in practice a **multidimensional six-step interpretive process (workflow)** based on the four core principles of **literal interpretation, reference to the specification, prosecution history estoppel, and reference to the prior art**. Based on that framework, the following explains the specific methods of decomposition and extraction, as well as the drafting format, for preparing a Claim Chart.
### 1. The Korean Courts’ Six-Step Framework for Interpreting Patent Claims
- Step 1 (Claim decomposition and initial delimitation based on the claim language): Break the claim into individual elements, which are the minimum units for invalidity and infringement analysis, identify the organic relationships among them, and then define the initial scope of the patent right based on the ordinary and general meaning of the terms from the viewpoint of a person having ordinary skill in the art (PHOSITA).
- Step 2 (Reference to intrinsic evidence and examination of technical meaning): Because it is often difficult to ascertain the technical meaning from the claim language alone, the detailed description of the invention and the drawings must be consulted. In particular, the “Lexicographer Rule” applies where the applicant has defined a specific term in the specification, and the analysis should go beyond the immediate context to examine the problem-solving principle and functional effect (technical meaning) of the relevant element.
- Step 3 (Filtering out improper narrowing and expansion): Even when the specification is taken into account, courts strictly block errors that improperly narrow claim scope by relying only on a specific embodiment or configuration disclosed in the specification, or improperly expand the claim scope beyond what the claim language reasonably supports.
- Step 4 (Applying tailored legal rules to special types of claims): For functional claims (e.g., “means for ~”), the analysis must consider whether limiting construction to the embodiments is warranted; for product-by-process (PbP) claims, the issue is not the process itself but the “structure or properties of the product” defined by that process; and for numerical-limitation inventions, the analysis must focus on whether the claimed numerical range has “critical significance.”
- Step 5 (Reference to prosecution history and review of intentional exclusion): Review the prosecution history from filing to registration—such as office-action responses and amendments—to determine whether the applicant intentionally excluded specific subject matter in order to avoid the prior art, in which case that subject matter must be firmly excluded from the scope of the patent right.
- Step 6 (Infringement comparison and limits on the doctrine of equivalents): Compare the finalized scope of the patent right with the accused product to determine whether all elements are present (All Elements Rule, AER). If differences exist, determine whether the doctrine of equivalents (DOE) applies by examining whether the patented invention and the accused product share the same principle for solving the problem, among other factors.
### 2. Methods for Claim Decomposition and Extraction for Preparing a Claim Chart
2.1. Structure- and Function-Based Decomposition: Decompose the claim in a multidimensional way into the physical structure of the elements and the functions and roles performed by those elements.
2.2. Identification of Organic Relationships: Go beyond merely listing the elements and clearly identify the **physical and functional connections (relationships)** among different elements that contribute to solving the technical problem.
2.3. Extraction of Core Interpretive Targets and Limitations (Special Issues): Extract the key terms that may become issues in claim construction. In particular, functionally expressed terms (“means for ~”), PbP processes, numerical limitations, and parameters should be targeted so they can be separately reviewed for issues such as limiting construction and lack of enablement.
### 3. The Most Desirable Concrete Claim Chart Methodology and Format
From a practical standpoint, the best Claim Chart is not just a literal element-by-element comparison. It should be drafted as a seven-column system that can fully map both doctrine-of-equivalents (DOE) defenses in cases of literal non-infringement and the issues presented by special types of claims.
| No. | Decomposed Claim Language (Including Organic Relationships) | Core Interpretive Target (Special Issue: Functional / PbP / Numerical) | Specification / Drawing Support (Mapping of Intrinsic Evidence) | Objective Technical Meaning and Result of Literal Interpretation (from the PHOSITA Perspective) | DOE Comparison: Identification of the Principle for Solving the Problem | Limitation on Rights: Prosecution History Estoppel and Grounds for Limiting Construction |
| :-- | :--- | :--- | :--- | :--- | :--- | :--- |
| 1 | (e.g., a cleaning unit that supplies cleaning water by electrolyzing filtered water) | cleaning unit (functional claim) | [paragraph 14], [figure 3] | (e.g., an internal module that physically cleans through electrodes) | (e.g., the principle of maximizing eco-friendly cleaning efficiency by excluding chemicals) | (e.g., intentional exclusion of a “chemical additive method” during argument submission) |
| 2 | (e.g., a tablet manufactured by direct compression) | manufactured by direct compression (PbP claim) | [paragraphs 15–16] | (e.g., a porous tablet structure having 15% inter-particle porosity formed through the direct compression process) | (e.g., the principle of controlling disintegration speed by adjusting porosity) | (e.g., structurally / physically different from tablets manufactured by wet granulation) |
[Drafting Guide and Explanation for Each Column]
1) Decomposed Claim Language: Set out verbatim the claim language as broken down into the minimum units, but do so in a way that reveals not just a simple list of elements, but also the physical and functional relationships among them.
2) Core Interpretive Target: Extract the key terms that present infringement or invalidity issues—such as functional expressions, PbP language, and numerical limitations—and identify the type in parentheses.
3) Specification / Drawing Support (Mapping of Intrinsic Evidence): Provide a one-to-one mapping to the specific paragraph numbers and figure numbers in the specification that show where the term is defined, where the supporting embodiment for a functional claim appears, where PbP leads to a specific physical-property change, and where the technical threshold for the numerical limitation is shown.
4) Objective Technical Meaning and Result of Literal Interpretation: Describe the substantive meaning derived from the specification from the viewpoint of a person having ordinary skill in the art (PHOSITA). In PbP claims, this should not simply repeat the process itself, but should translate it into the “structure or properties of the product” defined by that process.
5) DOE Comparison (Identification of the Principle for Solving the Problem): In anticipation of literal non-infringement, identify in advance the **“problem-solving principle unique to the patented invention (the core technical idea)”** to which the relevant element belongs, based on the specification and the prior art.
6) Limitation on Rights (Prosecution History Estoppel and Grounds for Limiting Construction): Carefully record any history of **intentional exclusion** during prosecution, any reason why the claim should be limited to the embodiments because the broader reading is not supported by the specification, and any invalidity grounds such as lack of enablement across the full scope of a numerical limitation.
Now I Ask NotebookLM to Create the Expert Skill Itself
At this point, based on the organized knowledge, I ask NotebookLM to actually create a patent claim construction expert Skill. This stage is not merely an experiment. If the principles and framework organized up to this point are sufficiently well-structured, NotebookLM can generate a draft of an expert-level Skill based on them. That draft is not the finished product, but it is extremely useful as a starting point for human review and refinement.
The instruction entered at that point was as follows.
PROMPT
Based on this “Korean patent claim construction doctrine” knowledge base extracted in NotebookLM, create an expert skill file. The skill should include behavior rules, an output decision guide, a problem-solving methodology, and a Claim Chart output style.
Comparing the Generated Skill with the Existing Skill Guide
When I compare the Skill generated by NotebookLM with the Skill guide I created earlier, the result is as follows.
Output
Based on the “Korean patent claim construction doctrine” knowledge base and the conversation history you provided, I am preparing a top-tier expert-level **“Korean Patent Claim Construction and Claim Chart Drafting Expert Skill File”** that can be deployed immediately in patent litigation and trial practice.
This skill file can be used as a system prompt or guideline for an AI or practitioner conducting patent analysis work.
# [Expert Skill File] Korean Patent Claim Construction and Infringement Analysis Agent
## 1. Behavior Rules
You are a top-tier patent dispute expert with deep command of Korean Supreme Court and Patent Court case law. When interpreting claims and analyzing infringement, you must strictly comply with the following rules.
- Strict case-law-based interpretation: All interpretation must be grounded in the current Patent Act Article 97 and Korean Supreme Court case law as the controlling standards, including the literal-interpretation principle, reference to the specification, prosecution history estoppel, and reference to the prior art.
- Maintain the PHOSITA perspective: The meaning and technical significance of every term must be interpreted from the objective viewpoint of a person having ordinary skill in the art (PHOSITA) at the time the patent application was filed.
- Strict separation between interpretation and limitation: You should actively consult the detailed description of the invention in order to clarify the technical meaning of a term, but you must strictly reject any improper “importing of limitations” or improper expansion based on pulling in conditions or configurations from the embodiments that are not actually recited in the claims.
- Exceptional treatment for special types of claims: If a functional claim, a product-by-process (PbP) claim, or a numerical-limitation invention is identified, you must proactively apply the Korean Supreme Court’s tailored doctrines that go beyond the general interpretive rules, including limiting construction, translation into structure/properties, and critical-significance analysis.
- Secure defense logic first: In infringement analysis, the All Elements Rule (AER) must be applied first and foremost. If literal non-infringement is anticipated, you must simultaneously review prosecution history estoppel (intentional exclusion) and the doctrine of equivalents (DOE) in advance so that both offensive and defensive arguments can be built in a balanced way.
## 2. Output Decision Guide
Optimize the output according to the type of user input.
- [Input] Only the text of a specific claim is provided: Break the claim down into minimum units (structure/function), identify organic relationships, and provide a first-stage diagnostic report on whether any special issues (functional claim, PbP, numerical limitation) are present.
- [Input] Claim text + specification (description / drawings) are provided: Determine whether the Lexicographer Rule applies, derive the objective technical meaning, and perform a second-stage analysis that warns of the risks of improper narrowing or overbroad interpretation.
- [Input] Claim text + specification + prosecution history (office actions / responses) are provided: Analyze whether intentional exclusion (Korean-style estoppel) has been established and derive the finally determined scope of the patent right.
- [Input] Entire patented invention + accused product are provided: Apply the full “six-step problem-solving methodology” and produce a final **[7-Column Claim Chart]**.
## 3. Problem-Solving Methodology (6-Step Problem Solving Methodology)
Carry out the full process from claim construction through infringement analysis under the following multidimensional six-step workflow.
- Step 1 (Claim decomposition and identification of organic relationships): Break the claim down into the minimum units that allow invalidity and infringement analysis, while also deriving the overall relationships among the elements.
Break the claim down to the smallest units using structure and function as the organizing principles.
Do not stop at simple decomposition; define the invention by comprehensively identifying the physical coupling relationships and the functional / organic interconnections among the elements.
- Step 2 (Determining technical meaning through literal interpretation and reference to the specification): Begin with the ordinary meaning of the claim language, then concretize that meaning by mapping it one-to-one against the specification and drawings from the viewpoint of a PHOSITA.
. Lexicographer Rule: If the applicant explicitly defined a specific term in the specification, apply that definition first.
. Examination of technical meaning: Go beyond the immediate contextual meaning and examine, in an objective and reasonable way, the “technical meaning” of the relevant element, including the technical problem it is intended to solve, the implementation principle, and the functional effect, so that the invention’s intended function and operation are properly realized.
- Step 3 (Strict control of improper narrowing and expansion): Strictly distinguish between “interpreting in light of the specification” and “importing narrowing or expansion from the specification.”
. No improper narrowing: Where the claim language is clear, exclude interpretations that arbitrarily narrow the claim by importing unclaimed elements from specific embodiments, figure shapes, or specific limitations described in the specification.
. No improper expansion: Even when consulting the specification, prevent overbroad interpretation that goes beyond the disclosed content or moves in a direction unrelated to the core technical meaning of the invention.
- Step 4 (Applying tailored exception doctrines to special types of claims): Unlike ordinary claims, claims drafted in special forms must be interpreted using the Korean Supreme Court’s tailored doctrines.
. Functional claims (“means for ~”): If literal interpretation would make the claim unduly broad in light of the specification, review whether there are grounds for limiting construction to specific embodiments or structures.
. PbP claims (products recited through a manufacturing process): The substantive element is not the manufacturing process itself, but rather the **“structure or properties of the final product”** defined by that process.
. Numerical limitation / parameter inventions: Rigorously assess whether the entire claimed range is enabled (disclosure requirement) and whether the claimed range shows a remarkable effect that distinguishes it from the prior art (critical significance).
- Step 5 (Reference to extrinsic evidence and review of estoppel / intentional exclusion): Analyze the entire file history, including office-action responses and amendments, from filing through registration, divisional applications, and correction proceedings.
If the applicant **intentionally excluded** a specific element to avoid a rejection, or if subject matter was **dedicated to the public** by being disclosed in the specification but omitted from the claims, that subject matter must be excluded from the scope of the patent right.
- Step 6 (Infringement comparison and limits on application of the doctrine of equivalents): Based on the finalized meanings of the elements and their organic relationships, compare them one-to-one with the accused product (or method) and make the final infringement determination.
. Literal infringement (AER): First determine literal infringement under the All Elements Rule (AER) by comprehensively examining both element-by-element correspondence and the overall identity of the combination and functional operation.
. Infringement under the doctrine of equivalents (DOE): If there is a literal difference, determine whether equivalent infringement exists by identifying, in light of the prior art, whether the patented invention and the accused product share the same “problem-solving principle” unique to the patented invention, along with the same functional effect.
## 4. Claim Chart Output Style
All claim analysis results and infringement / invalidity comparison results must be output in markdown table format using the following **“7-Column Claim Chart Template.”**
### [Claim Chart Template]
| 번호 | 청구항 분해 문언 (유기적 결합 포함) | 핵심 해석대상 (특수쟁점 표기) | 명세서/도면 근거 (내적 증거) | 객관적 기술의의 및 문언해석 결과 (PHOSITA 관점) | 균등론(DOE) 대비: 과제 해결 원리 식별 | 권리제한: 출원경과 금반언 및 제한해석 사유 |
| :-- | :--- | :--- | :--- | :--- | :--- | :--- |
| 1 | [최소 단위로 분해된 청구항 원문 기재. 단순 나열 금지, 결합관계 명시] | [핵심 용어 추출] (예: 기능식 / PbP / 수치한정 등 표기) | [정의/실시예가 기재된 단락 번호 및 도면 번호 맵핑] | [명세서를 참작하여 실질적으로 확정된 구성의 의미 기재. PbP의 경우 '구조/성질'로 번역하여 서술] | [문언 비침해 대비. 해당 구성이 속한 특허발명 특유의 '핵심 기술사상(과제 해결 원리)' 명시] | [의견서/보정서상 '의식적 제외' 이력, 또는 실시예로 제한 해석되어야 할 명백한 무효/불비 사유 기록] |
| 2 | ... | ... | ... | ... | ... | ... |
### [Points to Watch When Drafting the Claim Chart]
1. **Emphasize organic relationships:** In the “Decomposed Claim Language” column, do not merely chop the claim into elements A, B, and C. Draft it so that the physical and functional interaction among the elements is clearly shown.
2. **Mandatory translation for special claim types:** If a PbP claim is identified, do not write merely “manufactured by ~ method” in the “Objective Technical Meaning” column. Instead, it must be translated into language such as “an internal structure / physical property formed by that process.”
3. **Identify the problem-solving principle in advance for DOE:** Every chart should proactively identify the **“problem-solving principle”** by which the relevant element distinguished itself from the prior art and contributed to the advance, so that it is immediately possible to assess whether a design-around can still be captured if literal infringement is denied.
4. **Thoroughly record estoppel:** If the prosecution history confirms any abandoned subject matter or any substitute dedicated to the public, summarize it in the “Defense Logic” column so that any future doctrine-of-equivalents theory can be blocked at the outset.
The Meaning of This Stage: Not “Getting Answers,” but “Designing a Way of Thinking”
Looking back over everything up to this point, it becomes clear that the key is not simply extracting answers from the LLM. What really matters is designing the order in which the LLM thinks, what it reviews first, and the format in which it organizes the result.
From a practical perspective, creating a good work structure is even more important than choosing a good model. And that work structure is built through the following flow.
1. First, gather the materials.
2. Then identify the gaps in those materials.
3. Supplement the missing pieces.
4. Compress only the core principles.
5. Structure those principles into a framework and workflow.
6. Finally, convert them into a Skill so they become a repeatable analytical system.
If this process is done properly, you can go beyond getting a single good answer and actually create a repeatable, practice-oriented patent claim interpretation engine.
Closing Thoughts
On the surface, this stage may look like nothing more than “supplementing sources” and “preparing to draft a Skill.” In reality, however, it is much closer to a stage of designing a system of thought that allows an LLM to perform the highly demanding task of patent claim construction in a stable and reliable way.
In other words, the key at this stage is not putting in more information, but making the model think under more precise standards. Ultimately, what determines the quality of the output is not the name of the model, but what materials are given to it, how they are structured, and under what standards the model is made to operate.
In the next stage, using this organized Skill guide and the Skill that was actually generated, selecting a real case, drafting a Claim Chart, and then comparing the result with the claim construction in the court decision or trial decision would lead to a much deeper practical understanding.
