Triple
T32344891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael James Elstad |
E826429
|
entity |
| Predicate | caseHeWasInDecisionYear |
P97353
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Michael James Elstad, caseHeWasInDecisionYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseHeWasInDecisionYear Context triple: [Michael James Elstad, caseHeWasInDecisionYear, 1985]
-
A.
legalCaseHeParticipatedInDecisionYear
chosen
Indicates the year in which he participated in making the decision in a particular legal case.
-
B.
yearDecided
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
C.
caseDecidedIn
Indicates that a particular legal case was resolved or adjudicated within a specified court, jurisdiction, or decision-making body.
-
D.
caseDecidedBy
Indicates that a legal case is resolved or adjudicated by a specific decision-making authority, such as a judge or court.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:48 a.m.