Triple
T27173378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Shipping Co. v. Baker |
E682976
|
entity |
| Predicate | affectedParty |
P56117
|
FINISHED |
| Object | commercial fishermen in Alaska |
—
|
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: commercial fishermen in Alaska | Statement: [Exxon Shipping Co. v. Baker, affectedParty, commercial fishermen in Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedParty Context triple: [Exxon Shipping Co. v. Baker, affectedParty, commercial fishermen in Alaska]
-
A.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
B.
affectedEntity
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
-
C.
affectedCompany
Indicates that a company is impacted or influenced by a particular event, action, or entity.
-
D.
affectedAgency
Indicates that one entity has an effect on, or causes a change in, the agency or capacity for action of another entity.
-
E.
affectedPeople
chosen
Indicates the people who are impacted or influenced by a particular event, action, or condition.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 9:24 a.m.