Triple
T19354887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kivalina v. ExxonMobil |
E484115
|
entity |
| Predicate | plaintiffsSeek |
P2242
|
FINISHED |
| Object | damages for past and future harms |
—
|
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: damages for past and future harms | Statement: [Kivalina v. ExxonMobil, plaintiffsSeek, damages for past and future harms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaintiffsSeek Context triple: [Kivalina v. ExxonMobil, plaintiffsSeek, damages for past and future harms]
-
A.
remedySought
chosen
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
B.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
D.
soughtToRepresent
Indicates an attempt or intention by one entity to act on behalf of, stand in for, or present the interests of another entity.
-
E.
leadPlaintiffIn
Indicates that one entity serves as the primary or representative plaintiff in a legal case involving another entity.
- 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.