Triple
T401846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait of Magellan |
E9301
|
entity |
| Predicate | navigationalHazards |
P1950
|
FINISHED |
| Object | strong winds |
—
|
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: strong winds | Statement: [Strait of Magellan, navigationalHazards, strong winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalHazards Context triple: [Strait of Magellan, navigationalHazards, strong winds]
-
A.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
B.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
-
D.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
E.
hasHazardSignage
Indicates that appropriate warning or hazard signs are present to alert people to potential dangers associated with the entity.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec9f77888190bcc2bc68d201ed35 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.