Triple
T12587622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Drummond |
E300508
|
entity |
| Predicate | navigationAccess |
P44543
|
FINISHED |
| Object | via Feeder Ditch from Dismal Swamp Canal |
—
|
LITERAL 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: via Feeder Ditch from Dismal Swamp Canal | Statement: [Lake Drummond, navigationAccess, via Feeder Ditch from Dismal Swamp Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationAccess Context triple: [Lake Drummond, navigationAccess, via Feeder Ditch from Dismal Swamp Canal]
-
A.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
navigationFrom
chosen
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
D.
navigationSupport
Indicates that one entity provides assistance, guidance, or tools to help another entity navigate or find its way.
-
E.
navigationLockUse
Indicates the use or operation of a navigation lock by or for an entity, typically to enable passage through a controlled waterway segment.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:05 p.m.