Triple
T30871010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Dam |
E786336
|
entity |
| Predicate | waterBodyTypeFormed |
P21976
|
FINISHED |
| Object | reservoir |
—
|
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: reservoir | Statement: [Horseshoe Dam, waterBodyTypeFormed, reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyTypeFormed Context triple: [Horseshoe Dam, waterBodyTypeFormed, reservoir]
-
A.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
B.
formsBodyOfWater
Indicates that one entity constitutes or creates the physical substance or structure that makes up a particular body of water.
-
C.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
D.
waterBodyCreated
chosen
Indicates that one entity is responsible for the formation or creation of a particular body of water.
-
E.
hydronymType
Indicates the specific type or category of a water-related geographical name (e.g., river, lake, sea) associated with a hydronym.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 8:48 p.m.