Triple
T31589283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiran Strait |
E806043
|
entity |
| Predicate | strategicChokepoint |
P121975
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tiran Strait, strategicChokepoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicChokepoint Context triple: [Tiran Strait, strategicChokepoint, yes]
-
A.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
isStrategicCorridor
chosen
Indicates that a route, passage, or area serves as a critical pathway for movement, access, or control, giving it significant strategic importance.
-
C.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
D.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
E.
includesChokepoint
Indicates that one entity contains or encompasses a critical narrow passage or bottleneck area that can restrict or control movement or flow.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 10:27 p.m.