Triple
T18107389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Okeechobee Waterway |
E433379
|
entity |
| Predicate | hasLock |
P2431
|
FINISHED |
| Object | Port Mayaca Lock and Dam |
—
|
NE NERFINISHED |
How this triple was built (3 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: Port Mayaca Lock and Dam | Statement: [Lake Okeechobee Waterway, hasLock, Port Mayaca Lock and Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port Mayaca Lock and Dam Context triple: [Lake Okeechobee Waterway, hasLock, Port Mayaca Lock and Dam]
-
A.
Murray Lock and Dam
Murray Lock and Dam is a navigation and flood-control structure on the Arkansas River near Little Rock, Arkansas, that helps regulate river flow and support commercial barge traffic.
-
B.
Marmet Lock and Dam
Marmet Lock and Dam is a navigation and flood-control structure on the Kanawha River in West Virginia that helps maintain a stable waterway for commercial and recreational traffic.
-
C.
McNary Lock and Dam
McNary Lock and Dam is a navigation lock facility integrated into the McNary Dam complex on the Columbia River, enabling river traffic to bypass the dam.
-
D.
Aberdeen Lock and Dam
Aberdeen Lock and Dam is a navigation and flood-control structure on the Tennessee-Tombigbee Waterway in Mississippi that helps manage river traffic and water levels.
-
E.
Dresden Island Lock and Dam
Dresden Island Lock and Dam is a navigation and flood-control structure on the Illinois Waterway that helps regulate river levels and facilitate barge traffic in northeastern Illinois.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Port Mayaca Lock and Dam Target entity description: Port Mayaca Lock and Dam is a key navigation and water-control structure on Florida’s Lake Okeechobee Waterway, managing boat passage and regulating water levels between the lake and the St. Lucie Canal.
-
A.
Murray Lock and Dam
Murray Lock and Dam is a navigation and flood-control structure on the Arkansas River near Little Rock, Arkansas, that helps regulate river flow and support commercial barge traffic.
-
B.
Marmet Lock and Dam
Marmet Lock and Dam is a navigation and flood-control structure on the Kanawha River in West Virginia that helps maintain a stable waterway for commercial and recreational traffic.
-
C.
McNary Lock and Dam
McNary Lock and Dam is a navigation lock facility integrated into the McNary Dam complex on the Columbia River, enabling river traffic to bypass the dam.
-
D.
Aberdeen Lock and Dam
Aberdeen Lock and Dam is a navigation and flood-control structure on the Tennessee-Tombigbee Waterway in Mississippi that helps manage river traffic and water levels.
-
E.
Dresden Island Lock and Dam
Dresden Island Lock and Dam is a navigation and flood-control structure on the Illinois Waterway that helps regulate river levels and facilitate barge traffic in northeastern Illinois.
- F. None of above. chosen
Provenance (2 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
Created at: April 10, 2026, 10:28 a.m.