Triple
T27173308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exxon Valdez |
E682975
|
entity |
| Predicate | estimatedSpillVolume |
P78368
|
FINISHED |
| Object | approximately 11 million gallons |
—
|
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: approximately 11 million gallons | Statement: [Exxon Valdez, estimatedSpillVolume, approximately 11 million gallons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedSpillVolume Context triple: [Exxon Valdez, estimatedSpillVolume, approximately 11 million gallons]
-
A.
volumeSpilled
chosen
Indicates the quantity of a substance that has been unintentionally released or spilled from its container or source.
-
B.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
C.
spillType
Indicates the specific category or nature of a spill involved in the relationship or event.
-
D.
pressurizedVolume
Indicates that a specified volume is maintained at a pressure different from ambient (typically higher), often as part of a controlled or sealed system.
-
E.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:24 a.m.