Triple
T18372162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldred v. Ashcroft |
E446207
|
entity |
| Predicate | termInCitation |
P130874
|
FINISHED |
| Object | 537 U.S. 186 |
—
|
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: 537 U.S. 186 | Statement: [Eldred v. Ashcroft, termInCitation, 537 U.S. 186]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termInCitation Context triple: [Eldred v. Ashcroft, termInCitation, 537 U.S. 186]
-
A.
termInOfficeContext
Indicates that one entity’s tenure or period of holding an office, role, or position is being specified or contextualized in relation to another entity or timeframe.
-
B.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
C.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
D.
termOfProtection
Indicates the duration or conditions under which a right, protection, or legal safeguard remains in force.
-
E.
termFormalizedBy
Indicates that a given term has been formally defined, specified, or codified by a particular formalization (such as a formal theory, document, or system).
- F. None of above. chosen
Provenance (4 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51754539c819083f13b85cacb6cce |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:44 a.m.