Triple
T29361331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia and Eritrea |
E744598
|
entity |
| Predicate | borderCommission |
P195042
|
FINISHED |
| Object | Eritrea–Ethiopia Boundary Commission |
—
|
NE NERFINISHED |
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: Eritrea–Ethiopia Boundary Commission | Statement: [Ethiopia and Eritrea, borderCommission, Eritrea–Ethiopia Boundary Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCommission Context triple: [Ethiopia and Eritrea, borderCommission, Eritrea–Ethiopia Boundary Commission]
-
A.
boundaryCommissionsAffected
Indicates that certain boundary commissions are impacted or influenced as a result of the referenced action, event, or decision.
-
B.
borderDistribution
Indicates how a boundary or border is spatially arranged, divided, or allocated between adjacent entities.
-
C.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
D.
borderIntegration
Indicates the degree or manner in which two or more bordering regions are interconnected, coordinated, or functionally unified across their shared boundary.
-
E.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
- F. None of above. chosen
Provenance (4 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_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: April 28, 2026, 2:18 p.m.