Triple
T2456596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Congo War |
E54435
|
entity |
| Predicate | majorConsequence |
P812
|
FINISHED |
| Object | mass displacement of civilians |
—
|
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: mass displacement of civilians | Statement: [Second Congo War, majorConsequence, mass displacement of civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorConsequence Context triple: [Second Congo War, majorConsequence, mass displacement of civilians]
-
A.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
militaryConsequence
Indicates a causal relationship where one event, action, or condition leads to a specific outcome or effect in the military domain (such as changes in capability, strategy, or conflict status).
-
C.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
D.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
E.
majorStatus
Indicates that an entity holds primary or most significant status relative to others in a given context.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.