Triple
T23159089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantahala River |
E578528
|
entity |
| Predicate | waterFlowRegulatedBy |
P130170
|
FINISHED |
| Object | Nantahala Dam |
—
|
NE NERFINISHED |
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: Nantahala Dam | Statement: [Nantahala River, waterFlowRegulatedBy, Nantahala Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowRegulatedBy Context triple: [Nantahala River, waterFlowRegulatedBy, Nantahala Dam]
-
A.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
B.
waterFlowDependsOn
Indicates that the occurrence, direction, or amount of water flow is determined or constrained by another specified factor or condition.
-
C.
controlsWaterLevelOf
chosen
Indicates that one entity has the ability or authority to regulate or adjust the water level of another entity or system.
-
D.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
E.
waterDivertedThrough
Indicates that the flow of water is intentionally redirected from its original course to pass through a specified structure, channel, or location.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efeddd48190b6d03d2146583dcc |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.