Triple
T13576621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summersville Dam |
E324301
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Summersville Dam |
E324301
|
NE 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: Summersville Dam | Statement: [Summersville Dam, hasName, Summersville Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Summersville Dam Context triple: [Summersville Dam, hasName, Summersville Dam]
-
A.
Summersville Dam
chosen
Summersville Dam is a large rock-fill dam on the Gauley River in West Virginia, known for creating Summersville Lake and supporting popular whitewater recreation downstream.
-
B.
Leesville Dam
Leesville Dam is a hydroelectric and flood-control structure on the Roanoke River in Virginia that creates Leesville Lake.
-
C.
Smith Mountain Dam
Smith Mountain Dam is a hydroelectric and pumped-storage dam in Virginia that creates Smith Mountain Lake on the Roanoke River.
-
D.
Nolin River Dam
Nolin River Dam is a flood-control and recreation dam located on the Nolin River in central Kentucky, forming Nolin River Lake.
-
E.
South Holston Dam
South Holston Dam is a large Tennessee Valley Authority hydroelectric and flood-control dam on the South Fork Holston River in northeastern Tennessee.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff677935408190a28af4cd34d82aa4 |
completed | May 9, 2026, 4:57 p.m. |
Created at: April 9, 2026, 9:48 p.m.