Triple
T34410757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert G. Simmons |
E883256
|
entity |
| Predicate | endTime (ChiefJusticeOfNebraskaSupremeCourt) |
P104985
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Robert G. Simmons, endTime (ChiefJusticeOfNebraskaSupremeCourt), 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTime (ChiefJusticeOfNebraskaSupremeCourt) Context triple: [Robert G. Simmons, endTime (ChiefJusticeOfNebraskaSupremeCourt), 1963]
-
A.
endTime (chief justice)
chosen
Indicates the time at which the tenure or service of the chief justice concludes.
-
B.
endTime (as Chief Judge)
Indicates the time at which an entity’s role or tenure as Chief Judge concludes.
-
C.
endTime (Associate Justice of the South Carolina Supreme Court)
Indicates the date and time at which a person’s service as an Associate Justice of the South Carolina Supreme Court concludes.
-
D.
endTimeForPosition_AssociateJustice
Indicates the time at which an individual's tenure in the position of Associate Justice concludes.
-
E.
endTime (judicial service)
Indicates the point in time at which a judge’s period of judicial service concludes.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:59 a.m.