Triple
T37694078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Catron |
E938879
|
entity |
| Predicate | servedUnderChiefJustice |
P202413
|
FINISHED |
| Object | Roger B. Taney |
—
|
NE NERFINISHED |
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: Roger B. Taney | Statement: [John Catron, servedUnderChiefJustice, Roger B. Taney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedUnderChiefJustice Context triple: [John Catron, servedUnderChiefJustice, Roger B. Taney]
-
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.
chiefJusticePresiding
Indicates that a specified chief justice is the one formally presiding over a particular court session, case, or judicial proceeding.
-
C.
succeededByAsChiefJustice
Indicates that one individual directly followed another in the role of Chief Justice.
-
D.
hasChiefJudge
Indicates that an entity holds the role or position of chief judge for another entity (such as a court or judicial body).
-
E.
servedOnSupremeCourtUntil
Indicates that an individual held a position on the Supreme Court up to and including a specified end date.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
| PDg | Predicate description generation | batch_6a007aa82810819080bb16dd5022c324 |
completed | May 10, 2026, 12:31 p.m. |
Created at: May 3, 2026, 4:18 p.m.