Triple
T3704734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trent Falls |
E80863
|
entity |
| Predicate | navigationalStatus |
P43177
|
FINISHED |
| Object | hazardous for shipping |
—
|
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: hazardous for shipping | Statement: [Trent Falls, navigationalStatus, hazardous for shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalStatus Context triple: [Trent Falls, navigationalStatus, hazardous for shipping]
-
A.
navigationStatus
Indicates the current state or condition of an entity’s navigation process, such as whether it is actively navigating, idle, or has encountered an issue.
-
B.
hasNavigationStatus
chosen
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
C.
navigableFrom
Indicates that one location or entity can be reached or traversed from another, typically via a valid path, route, or connection.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54bbfcc8190bec9c16e3749c3b1 |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.