Triple
T7702803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Valdez oil spill |
E174539
|
entity |
| Predicate | shorelineHeavilyOiledLength |
P78369
|
FINISHED |
| Object | about 200 miles |
—
|
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: about 200 miles | Statement: [Exxon Valdez oil spill, shorelineHeavilyOiledLength, about 200 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineHeavilyOiledLength Context triple: [Exxon Valdez oil spill, shorelineHeavilyOiledLength, about 200 miles]
-
A.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
numberOfShoreEstablishmentsInvolved
Indicates the count of shore-based establishments that are involved in or associated with a particular event, operation, or context.
-
C.
hasShoreLengthOn
Indicates that an entity has a specified length of shoreline along or bordering another geographic feature (such as a body of water or coast).
-
D.
hasStructureOnShore
Indicates that a structure is located on or directly adjacent to the shore of a body of water.
-
E.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
- F. None of above. chosen
Provenance (4 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:03 p.m.