Triple
T8565583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijan People's Government |
E202793
|
entity |
| Predicate | reasonForSupport |
P24494
|
FINISHED |
| Object | Soviet strategic interest in northern Iran |
—
|
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: Soviet strategic interest in northern Iran | Statement: [Azerbaijan People's Government, reasonForSupport, Soviet strategic interest in northern Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSupport Context triple: [Azerbaijan People's Government, reasonForSupport, Soviet strategic interest in northern Iran]
-
A.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
C.
reasonForPledge
Indicates the motivation or justification behind making a particular pledge or commitment.
-
D.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d2331881909d92ddde90f580e9 |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.