Triple
T9611486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf Intracoastal Waterway |
E232111
|
entity |
| Predicate | hasTypicalChannelWidth |
P19786
|
FINISHED |
| Object | 125 feet |
—
|
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: 125 feet | Statement: [Gulf Intracoastal Waterway, hasTypicalChannelWidth, 125 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalChannelWidth Context triple: [Gulf Intracoastal Waterway, hasTypicalChannelWidth, 125 feet]
-
A.
typicalWidth
chosen
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
B.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
C.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
E.
hasRailWidth
Indicates that one entity has a specified width measurement for its rail or rails.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a87764481909ab96cd2ab96d14b |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:09 p.m.