Triple
T26342359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morrow Point Reservoir |
E662679
|
entity |
| Predicate | damTypeAtOutlet |
P15960
|
FINISHED |
| Object | concrete double-curvature arch dam |
—
|
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: concrete double-curvature arch dam | Statement: [Morrow Point Reservoir, damTypeAtOutlet, concrete double-curvature arch dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damTypeAtOutlet Context triple: [Morrow Point Reservoir, damTypeAtOutlet, concrete double-curvature arch dam]
-
A.
typeOfDam
chosen
Indicates the specific kind or classification of a dam associated with an entity.
-
B.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
C.
typeOfDamSystem
Indicates that one entity is a classification or kind of dam system to which the other entity belongs or corresponds.
-
D.
drainageOutlet
Indicates that one entity serves as the point where fluids or runoff are discharged or exit from another entity.
-
E.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa3f27c8190a6f4223beb94a82e |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:39 p.m.