Triple
T8251713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Nile State |
E192972
|
entity |
| Predicate | conflictLinkedTo |
P1406
|
FINISHED |
| Object | center–periphery tensions in Sudan |
—
|
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: center–periphery tensions in Sudan | Statement: [Blue Nile State, conflictLinkedTo, center–periphery tensions in Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictLinkedTo Context triple: [Blue Nile State, conflictLinkedTo, center–periphery tensions in Sudan]
-
A.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
B.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
-
D.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78ca4b0881909bb1fb550dba59e7 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.