Triple
T3868800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Lock |
E91926
|
entity |
| Predicate | enablesTrafficType |
P26781
|
FINISHED |
| Object | commercial vessels |
—
|
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: commercial vessels | Statement: [Kentucky Lock, enablesTrafficType, commercial vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesTrafficType Context triple: [Kentucky Lock, enablesTrafficType, commercial vessels]
-
A.
supportsTraffic
chosen
Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
-
B.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
C.
allowedTransport
Indicates that a particular mode or means of transport is permitted for use between the related entities.
-
D.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
E.
hasTrafficFunction
Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3dfb3c8190a0a07070f0d76bf6 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.