Triple
T31584470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Armenia corridor |
E805918
|
entity |
| Predicate | strategicForCountry |
P46323
|
FINISHED |
| Object | Iran |
—
|
NE NERFINISHED |
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: Iran | Statement: [Iran–Armenia corridor, strategicForCountry, Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicForCountry Context triple: [Iran–Armenia corridor, strategicForCountry, Iran]
-
A.
countryStrategyContext
Indicates the strategic context or framework within which a country’s actions, policies, or decisions are planned and interpreted.
-
B.
strategicAspect
Indicates that something pertains to a strategic dimension, such as long-term planning, positioning, or high-level decision-making within a broader context.
-
C.
strategizesFor
Indicates that one entity plans or devises strategies on behalf of, or in support of, another entity.
-
D.
strategicFactors
Indicates that certain elements or conditions significantly influence the planning, direction, or outcome of a broader strategy or long-term objective.
-
E.
strategicArea
chosen
Indicates that an entity is designated as an area of strategic importance or priority within a broader plan, operation, or context.
- 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_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 10:25 p.m.