Triple
T2825705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monongahela River |
E54914
|
entity |
| Predicate | hasLockAndDamSystem |
P43272
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Monongahela River, hasLockAndDamSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockAndDamSystem Context triple: [Monongahela River, hasLockAndDamSystem, yes]
-
A.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
-
B.
hasSpillway
Indicates that a dam or similar water-retaining structure is equipped with a spillway for controlled release or overflow of water.
-
C.
reservoirCreatedByDam
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
D.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
-
E.
hasMajorReservoir
Indicates that an entity possesses or is associated with a primary or significant reservoir (such as a large storage or accumulation of a resource).
- F. None of above. chosen
Provenance (4 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde925e688190bb390d3182f8c4f0 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:59 p.m.