Triple
T2453511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Intracoastal Waterway |
E53761
|
entity |
| Predicate | navigationalAid |
P8170
|
FINISHED |
| Object | channel markers |
—
|
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: channel markers | Statement: [Atlantic Intracoastal Waterway, navigationalAid, channel markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalAid Context triple: [Atlantic Intracoastal Waterway, navigationalAid, channel markers]
-
A.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
-
B.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
C.
hasNavigationAid
chosen
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
D.
navigationClearanceType
Indicates the specific type or category of clearance granted for a navigation-related operation or movement.
-
E.
navigability
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.