Triple
T30846498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilayat al-Yaman |
E785647
|
entity |
| Predicate | typeOfConflictActivity |
P1397
|
FINISHED |
| Object | insurgency |
—
|
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: insurgency | Statement: [Wilayat al-Yaman, typeOfConflictActivity, insurgency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictActivity Context triple: [Wilayat al-Yaman, typeOfConflictActivity, insurgency]
-
A.
conflictActivity
Indicates that an entity is engaged in, associated with, or affected by a conflict-related action or event.
-
B.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
typeOfConflictTransition
Indicates a change from one type or category of conflict to another within a conflict’s progression or lifecycle.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: April 29, 2026, 8:46 p.m.