Triple
T17358078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrean–Djiboutian border |
E421993
|
entity |
| Predicate | conflictOccurredInYear |
P66456
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Eritrean–Djiboutian border, conflictOccurredInYear, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictOccurredInYear Context triple: [Eritrean–Djiboutian border, conflictOccurredInYear, 2008]
-
A.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
B.
majorConflictYear
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
-
C.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
-
D.
yearInConflict
chosen
Indicates the specific year or years during which a given conflict took place or was actively ongoing.
-
E.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4a37788190b330b7207aa424b6 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.