Triple
T7702802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Valdez oil spill |
E174539
|
entity |
| Predicate | shorelineContaminatedLength |
P1568
|
FINISHED |
| Object | over 1,300 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: over 1,300 miles | Statement: [Exxon Valdez oil spill, shorelineContaminatedLength, over 1,300 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineContaminatedLength Context triple: [Exxon Valdez oil spill, shorelineContaminatedLength, over 1,300 miles]
-
A.
shorelineLength
chosen
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
C.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
D.
shorelineCharacteristic
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
E.
protectedAreaOnShore
Indicates that a protected area is located on or along a shoreline.
- 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_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. |
Created at: March 27, 2026, 4:03 p.m.