Triple
T28287931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltiysk Strait |
E713337
|
entity |
| Predicate | hasStrategicUse |
P39800
|
FINISHED |
| Object | Russian Baltic Fleet access |
—
|
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: Russian Baltic Fleet access | Statement: [Baltiysk Strait, hasStrategicUse, Russian Baltic Fleet access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrategicUse Context triple: [Baltiysk Strait, hasStrategicUse, Russian Baltic Fleet access]
-
A.
hasStrategicFunction
Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
-
B.
isStrategicWeapon
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
C.
hasStrategicImportanceType
Indicates that something is classified according to a specific category or type of strategic importance.
-
D.
hasStrategicPass
chosen
Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
-
E.
hasStrategicContext
Indicates that something is associated with or situated within a broader strategic framework, plan, or set of objectives.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 11:27 p.m.