Triple
T21434646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian federal member states |
E528774
|
entity |
| Predicate | mayBorder |
P43209
|
FINISHED |
| Object | neighboring countries of Ethiopia |
—
|
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: neighboring countries of Ethiopia | Statement: [Ethiopian federal member states, mayBorder, neighboring countries of Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBorder Context triple: [Ethiopian federal member states, mayBorder, neighboring countries of Ethiopia]
-
A.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
B.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
relatedBorder
chosen
Indicates that two geographic or political entities share a common boundary or border with each other.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b53516d081908f8058a8ee363629 |
completed | April 22, 2026, 11:47 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6 p.m.