Triple
T27173340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Shipping Co. v. Baker |
E682976
|
entity |
| Predicate | aroseFromLocation |
P48990
|
FINISHED |
| Object | Prince William Sound, Alaska |
—
|
NE NERFINISHED |
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: Prince William Sound, Alaska | Statement: [Exxon Shipping Co. v. Baker, aroseFromLocation, Prince William Sound, Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aroseFromLocation Context triple: [Exxon Shipping Co. v. Baker, aroseFromLocation, Prince William Sound, Alaska]
-
A.
introducedFromLocation
Indicates that something or someone was brought, initiated, or first made present starting from a specified location.
-
B.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target entity.
-
C.
arisesIn
chosen
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
D.
createdAtLocation
Indicates the place or location where an entity was originally created or brought into existence.
-
E.
originalLocationEvent
Indicates that an event occurred at or is associated with the place where an entity was originally located or originated.
- 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_69f62549039c8190af7159d07416c985 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:24 a.m.