Triple
T1003574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William H. Rehnquist |
E21657
|
entity |
| Predicate | swornInAsAssociateJusticeOn |
P22199
|
FINISHED |
| Object | 1972-01-07 |
—
|
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: 1972-01-07 | Statement: [William H. Rehnquist, swornInAsAssociateJusticeOn, 1972-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: swornInAsAssociateJusticeOn Context triple: [William H. Rehnquist, swornInAsAssociateJusticeOn, 1972-01-07]
-
A.
chiefJustice
Indicates that one entity serves as the chief justice (the highest-ranking judicial officer) of another entity, such as a court or jurisdiction.
-
B.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
C.
chiefJusticeSinceYear
Indicates that an entity has held the position of chief justice starting from a specified year.
-
D.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
E.
numberOfAssociateJustices
Indicates the total count of associate justices associated with a given judicial body or court.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fe0a548190aee8abf1890e141e |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.