Triple
T37143431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbott v. Burke line of cases |
E920176
|
entity |
| Predicate | originatingCase |
P205758
|
FINISHED |
| Object | Abbott v. Burke (Abbott I) |
E920176
|
NE 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: Abbott v. Burke (Abbott I) | Statement: [Abbott v. Burke line of cases, originatingCase, Abbott v. Burke (Abbott I)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingCase Context triple: [Abbott v. Burke line of cases, originatingCase, Abbott v. Burke (Abbott I)]
-
A.
originatingJurisdiction
Indicates the jurisdiction (such as a country, state, or legal authority) from which something originally comes or under whose laws it was first established.
-
B.
originatingStateCourt
Indicates the court in which a legal case or proceeding was originally filed or initiated.
-
C.
originatedInCourt
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
D.
originatingJudge
Indicates the judge who initially handled or issued the original decision or order in a legal matter.
-
E.
originatedInCourtOf
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
- F. None of above. chosen
Provenance (5 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f6a2d35848190b6410e4ac53df115 |
completed | June 27, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.