Triple
T15414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruth Bader Ginsburg |
E307
|
entity |
| Predicate | endTime (D.C. Circuit judgeship) |
P214
|
FINISHED |
| Object | 1993-08-09 |
—
|
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: 1993-08-09 | Statement: [Ruth Bader Ginsburg, endTime (D.C. Circuit judgeship), 1993-08-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTime (D.C. Circuit judgeship) Context triple: [Ruth Bader Ginsburg, endTime (D.C. Circuit judgeship), 1993-08-09]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
D.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
E.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23feae8c481908d8c50faac01fc5c |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.