Triple
T1739488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James C. McReynolds |
E38198
|
entity |
| Predicate | endTime (as Attorney General) |
P31763
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [James C. McReynolds, endTime (as Attorney General), 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTime (as Attorney General) Context triple: [James C. McReynolds, endTime (as Attorney General), 1914]
-
A.
endTimeAsSolicitorGeneral
Indicates the date and time at which an individual’s service in the role of Solicitor General comes to an end.
-
B.
endTime (Tenth Circuit)
Indicates the point in time at which an event, action, or legally relevant period concludes within the Tenth Circuit context.
-
C.
endTimeForPosition:Director of Public Prosecutions
Indicates the point in time at which an individual’s tenure in the position of Director of Public Prosecutions concludes.
-
D.
endTimeForPosition_AssociateJustice
Indicates the time at which an individual's tenure in the position of Associate Justice concludes.
-
E.
startTimeAsSolicitorGeneral
Indicates the point in time when an individual began serving in the role of Solicitor General.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab3c2479148190badc616f8e2686d4 |
completed | March 6, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:30 p.m.