Triple
T29361329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia and Eritrea |
E744598
|
entity |
| Predicate | borderConflictPeriod |
P28865
|
FINISHED |
| Object | 1998–2000 |
—
|
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: 1998–2000 | Statement: [Ethiopia and Eritrea, borderConflictPeriod, 1998–2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderConflictPeriod Context triple: [Ethiopia and Eritrea, borderConflictPeriod, 1998–2000]
-
A.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
B.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
C.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
-
D.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
-
E.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 28, 2026, 2:18 p.m.