Triple
T26086672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panjdeh Oasis |
E658000
|
entity |
| Predicate | conflictCasusBelli |
P11716
|
FINISHED |
| Object | dispute over Afghan frontier delimitation |
—
|
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: dispute over Afghan frontier delimitation | Statement: [Panjdeh Oasis, conflictCasusBelli, dispute over Afghan frontier delimitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictCasusBelli Context triple: [Panjdeh Oasis, conflictCasusBelli, dispute over Afghan frontier delimitation]
-
A.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
B.
casusBelli
Indicates a relationship where one entity serves as the cause, justification, or pretext for another entity to initiate conflict or war.
-
C.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
D.
casusBelliFor
chosen
Indicates that one entity serves as the justification or cause for another entity to initiate conflict, often war or hostilities.
-
E.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6070013bc81908053ea20f7c7d71b |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:43 p.m.