Triple
T29009044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenia Alliance |
E736512
|
entity |
| Predicate | foreignPolicyPosition |
P23116
|
FINISHED |
| Object | pro‑Russian |
—
|
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: pro‑Russian | Statement: [Armenia Alliance, foreignPolicyPosition, pro‑Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignPolicyPosition Context triple: [Armenia Alliance, foreignPolicyPosition, pro‑Russian]
-
A.
positionOnForeignPolicy
chosen
Indicates a stance or viewpoint an entity holds regarding international relations, diplomacy, and global political issues.
-
B.
foreignPolicyArea
Indicates the specific domain or topic within foreign policy to which an action, decision, or statement is related.
-
C.
foreignPolicyCharacteristic
Indicates a defining feature or quality of an entity’s foreign policy.
-
D.
foreignPolicySignificance
Indicates the extent to which something is important or consequential within the realm of a state’s foreign policy decisions and international relations.
-
E.
foreignPolicyProgram
Indicates a program or initiative that defines, guides, or implements a state's foreign policy toward other international actors.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fda92188190b20bfd59902ed27d |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:40 a.m.