Triple
T14165681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leahy–Smith America Invents Act |
E351066
|
entity |
| Predicate | systemReplaced |
P3618
|
FINISHED |
| Object | first-to-invent patent system |
—
|
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: first-to-invent patent system | Statement: [Leahy–Smith America Invents Act, systemReplaced, first-to-invent patent system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemReplaced Context triple: [Leahy–Smith America Invents Act, systemReplaced, first-to-invent patent system]
-
A.
replacedSystemBasedOn
Indicates that one system was substituted for another specifically on the basis of certain criteria, conditions, or evaluations.
-
B.
replacedPlatform
Indicates that one platform has been superseded or taken over by another platform.
-
C.
replacedInSystemVersion
Indicates that one entity has been superseded or substituted by another in a specific version of a system.
-
D.
replacedSystemUsedUntil
chosen
Indicates that one system was used up until it was replaced by another system.
-
E.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1 a.m.