Triple
T12879114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Faw |
E308041
|
entity |
| Predicate | strategicCategory |
P94174
|
FINISHED |
| Object | chokepoint for Iraqi maritime 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: chokepoint for Iraqi maritime access | Statement: [Al-Faw, strategicCategory, chokepoint for Iraqi maritime access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicCategory Context triple: [Al-Faw, strategicCategory, chokepoint for Iraqi maritime access]
-
A.
strategicArea
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
-
B.
strategicStatus
chosen
Indicates the strategic condition or importance of an entity within a broader plan, context, or objective.
-
C.
strategicStance
Indicates the overarching strategic position, approach, or orientation an entity adopts in relation to others or to a particular situation.
-
D.
strategicReason
Indicates that one entity serves as a reason, justification, or motivation for another entity’s strategic decision, plan, or action.
-
E.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.