Triple
T16043941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrea–Ethiopia border |
E389166
|
entity |
| Predicate | UNMissionStart |
P14315
|
FINISHED |
| Object | 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: 2000 | Statement: [Eritrea–Ethiopia border, UNMissionStart, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNMissionStart Context triple: [Eritrea–Ethiopia border, UNMissionStart, 2000]
-
A.
missionStart
chosen
Indicates the point in time or event at which a mission or task officially begins.
-
B.
UNMission
Indicates that an entity is a United Nations peacekeeping or political mission operating in a specific area or context.
-
C.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
D.
firstReplacementMission
Indicates that an entity serves as the initial replacement in a sequence of missions or assignments for another entity.
-
E.
launchOnMission
Indicates initiating the sending of an entity (typically a vehicle, spacecraft, or device) to carry out a specific mission or operation.
- 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.