Triple
T19354891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kivalina v. ExxonMobil |
E484115
|
entity |
| Predicate | districtCourtOutcome |
P2931
|
FINISHED |
| Object | case dismissed |
—
|
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: case dismissed | Statement: [Kivalina v. ExxonMobil, districtCourtOutcome, case dismissed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtCourtOutcome Context triple: [Kivalina v. ExxonMobil, districtCourtOutcome, case dismissed]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
C.
legalCaseHeParticipatedInDecidedBy
Indicates that a legal case in which he participated was decided or adjudicated by a specified authority or court.
-
D.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
courtOrdered
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190794188190a94de464d985b5fd |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.