Triple
T32956567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen Lock and Dam |
E843116
|
entity |
| Predicate | managesWaterLevelsOn |
P130170
|
FINISHED |
| Object | Tennessee-Tombigbee Waterway |
—
|
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: Tennessee-Tombigbee Waterway | Statement: [Aberdeen Lock and Dam, managesWaterLevelsOn, Tennessee-Tombigbee Waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesWaterLevelsOn Context triple: [Aberdeen Lock and Dam, managesWaterLevelsOn, Tennessee-Tombigbee Waterway]
-
A.
controlsWaterLevelOf
chosen
Indicates that one entity has the ability or authority to regulate or adjust the water level of another entity or system.
-
B.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
C.
managesReservoir
Indicates that one entity is responsible for overseeing, operating, and controlling the use or condition of a reservoir.
-
D.
hasWaterManagementStructure
Indicates that one entity possesses, contains, or is associated with a built feature used to control, store, convey, or manage water.
-
E.
hasNormalWaterLevel
Indicates that an entity’s water level is within the expected or standard range, neither abnormally high nor low.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:21 a.m.