Triple
T36249646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Devil Mine |
E891761
|
entity |
| Predicate | waterBodyImpacted |
P90970
|
FINISHED |
| Object | Kuskokwim River |
—
|
NE NERFINISHED |
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: Kuskokwim River | Statement: [Red Devil Mine, waterBodyImpacted, Kuskokwim River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyImpacted Context triple: [Red Devil Mine, waterBodyImpacted, Kuskokwim River]
-
A.
affectsWaterBody
chosen
Indicates that one entity has an impact on the condition, quality, or state of a water body.
-
B.
bodyOfWaterThreateningOriginalSite
Indicates that a body of water poses a risk of damage, flooding, or destruction to the original location or site.
-
C.
waterLevelAffectedBy
Indicates that the water level of one entity changes as a result of the influence or impact of another entity or factor.
-
D.
flowsIntoBodyOfWaterAt
Indicates that one body of water moves or drains into another body of water at a specific location or point.
-
E.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:09 p.m.