Triple
T19556497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ickles Lock |
E489325
|
entity |
| Predicate | isInlandWaterwayStructure |
P4361
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ickles Lock, isInlandWaterwayStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInlandWaterwayStructure Context triple: [Ickles Lock, isInlandWaterwayStructure, true]
-
A.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
B.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
C.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
-
D.
hasStructureOnWatercourse
chosen
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
E.
isInternationalWaterway
Indicates that a waterway is recognized as lying beyond the territorial jurisdiction of any single state and is subject to international navigation or legal regimes.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d341d708190b8ef35822f8bfe7c |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.