Triple
T29561488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Chumar standoff |
E750050
|
entity |
| Predicate | escalationRisk |
P103824
|
FINISHED |
| Object | potential for wider armed conflict |
—
|
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: potential for wider armed conflict | Statement: [2014 Chumar standoff, escalationRisk, potential for wider armed conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escalationRisk Context triple: [2014 Chumar standoff, escalationRisk, potential for wider armed conflict]
-
A.
escalationDetail
Indicates that additional information is provided about how, why, or to what extent a situation, issue, or conflict has intensified or been elevated.
-
B.
conflictRisk
chosen
Indicates a likelihood or potential for disagreement, tension, or conflict to arise between the related entities.
-
C.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
D.
riskHighlighted
Indicates that a particular risk has been identified and specially marked for attention or emphasis.
-
E.
escalationDate
Indicates the date on which an issue, case, or situation was formally escalated to a higher level of attention or authority.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1d90d0819096fd1592bed2f6d9 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:20 p.m.