Triple
T28403779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prestige oil spill |
E719461
|
entity |
| Predicate | pollutedArea |
P48801
|
FINISHED |
| Object | Galician coast |
—
|
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: Galician coast | Statement: [Prestige oil spill, pollutedArea, Galician coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pollutedArea Context triple: [Prestige oil spill, pollutedArea, Galician coast]
-
A.
targetPollutant
Indicates that something is the specific pollutant that is being aimed at, affected, or addressed by an action, process, or regulation.
-
B.
pollutant
Indicates that one entity is a substance or factor that contaminates or degrades the quality of another entity or environment.
-
C.
wasHeavilyPollutedDuring
Indicates that a place or environment experienced a high level of pollution during a specified time period.
-
D.
pollutionSource
chosen
Indicates that one entity is the origin or cause of pollution affecting another entity or environment.
-
E.
historicallyPollutedBy
Indicates that an entity has experienced pollution in the past as a result of actions or emissions from another entity.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d6e29388190a285f0ff5bc70a3f |
completed | May 2, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:22 a.m.