Triple
T25614535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patent Act of 1952 |
E642122
|
entity |
| Predicate | introducedSection |
P83636
|
FINISHED |
| Object | 35 U.S.C. § 101 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 35 U.S.C. § 101 | Statement: [Patent Act of 1952, introducedSection, 35 U.S.C. § 101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedSection Context triple: [Patent Act of 1952, introducedSection, 35 U.S.C. § 101]
-
A.
sectionIntroduced
chosen
Indicates that a particular section was introduced or added at a specific point in time or context.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedPart
Indicates that one entity has brought another entity into existence, use, or awareness as a component or element of something.
-
D.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
E.
hasIntroduction
Indicates that one entity includes or provides an introductory section, part, or presentation for another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 4:58 p.m.