Triple
T25881421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John G. Heyburn II |
E652058
|
entity |
| Predicate | startTimeChiefJudge |
P176260
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [John G. Heyburn II, startTimeChiefJudge, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeChiefJudge Context triple: [John G. Heyburn II, startTimeChiefJudge, 2001]
-
A.
startTimeAsCircuitJudge
Indicates the point in time at which an individual begins serving in the role of a circuit judge.
-
B.
startTime (Chief Judge SDNY)
Indicates the specific time at which the tenure or role of the Chief Judge of the Southern District of New York begins.
-
C.
startTimeOfPosition_ChiefJudgeFirstCircuit
Indicates the date and time when an individual began serving in the position of Chief Judge of the First Circuit.
-
D.
judgesServeUntil
Indicates that a judge continues to hold and perform their judicial office up to a specified end date or condition.
-
E.
officeStartTimeAsChiefJudgeOfDCCircuit
Indicates the date and time when an individual began serving as Chief Judge of the D.C. Circuit.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 22, 2026, 8:16 a.m.