Triple

T10841762
Position Surface form Disambiguated ID Type / Status
Subject South Holston Lake E255903 entity
Predicate formedBy P972 FINISHED
Object South Holston Dam E265533 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: South Holston Dam | Statement: [South Holston Lake, formedBy, South Holston Dam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: South Holston Dam
Context triple: [South Holston Lake, formedBy, South Holston Dam]
  • A. South Holston Dam chosen
    South Holston Dam is a large Tennessee Valley Authority hydroelectric and flood-control dam on the South Fork Holston River in northeastern Tennessee.
  • B. Leesville Dam
    Leesville Dam is a hydroelectric and flood-control structure on the Roanoke River in Virginia that creates Leesville Lake.
  • C. Apalachia Dam
    Apalachia Dam is a hydroelectric dam in western North Carolina that impounds the Hiwassee River to generate power and help manage regional water resources.
  • D. Smith Mountain Dam
    Smith Mountain Dam is a hydroelectric and pumped-storage dam in Virginia that creates Smith Mountain Lake on the Roanoke River.
  • E. 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.
  • 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_69d6aa81a5d08190aa86689061d1ddd2 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d750ccb95c81908fec4885e6172f78 completed April 9, 2026, 7:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69e6849dbff08190a352eaaea8606bdb completed April 20, 2026, 7:55 p.m.
Created at: April 8, 2026, 9:19 p.m.