Triple
T21348579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drift River |
E526408
|
entity |
| Predicate | nearbyInfrastructureUse |
P124983
|
FINISHED |
| Object | oil storage |
—
|
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: oil storage | Statement: [Drift River, nearbyInfrastructureUse, oil storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyInfrastructureUse Context triple: [Drift River, nearbyInfrastructureUse, oil storage]
-
A.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
B.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
C.
hasNearbyInfrastructureType
chosen
Indicates that an entity is located close to infrastructure of a specified type.
-
D.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
E.
adjacentToInfrastructure
Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baab4e081908916a289c607cf3a |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:02 p.m.