Triple
T10875794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darfur region |
E256794
|
entity |
| Predicate | conflictBegan |
P44953
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Darfur region, conflictBegan, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictBegan Context triple: [Darfur region, conflictBegan, 2003]
-
A.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
B.
conflictBeganInYear
chosen
Indicates that the specified conflict started or first broke out in the given calendar year.
-
C.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
D.
originatingConflict
Indicates the conflict or dispute from which another event, situation, or relationship initially arises or is caused.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ac901881909938cabe4d21bdbf |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.