Triple
T401845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait of Magellan |
E9301
|
entity |
| Predicate | navigability |
P13009
|
FINISHED |
| Object | navigable |
—
|
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: navigable | Statement: [Strait of Magellan, navigability, navigable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigability Context triple: [Strait of Magellan, navigability, navigable]
-
A.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
D.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a2eb7c56bc8190ab787801af2eec8d |
completed | Feb. 28, 2026, 1:19 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.