Triple
T16043908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badme region |
E389165
|
entity |
| Predicate | postConflictTensionPersistedUntil |
P17908
|
FINISHED |
| Object | 2018 Eritrea–Ethiopia rapprochement |
—
|
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: 2018 Eritrea–Ethiopia rapprochement | Statement: [Badme region, postConflictTensionPersistedUntil, 2018 Eritrea–Ethiopia rapprochement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postConflictTensionPersistedUntil Context triple: [Badme region, postConflictTensionPersistedUntil, 2018 Eritrea–Ethiopia rapprochement]
-
A.
postConflictContext
Indicates that the relationship or action occurs within, or is shaped by, a setting that follows the end of an armed conflict or violent confrontation.
-
B.
postConflictStatus
chosen
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
-
C.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
E.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.