Triple
T34219121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia–Djibouti border |
E877875
|
entity |
| Predicate | landlocksSide |
P178540
|
FINISHED |
| Object | Ethiopia |
—
|
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: Ethiopia | Statement: [Ethiopia–Djibouti border, landlocksSide, Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landlocksSide Context triple: [Ethiopia–Djibouti border, landlocksSide, Ethiopia]
-
A.
landlocked
Indicates that a place has no direct access to the open sea or ocean, being entirely surrounded by land or enclosed bodies of water.
-
B.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
C.
landVariant
Indicates that one landform, terrain type, or land-related entity is an alternative or variant form of another.
-
D.
landLegSystem
Indicates a relationship where a landing system is specifically designed for or associated with a leg-based support or landing mechanism.
-
E.
landAction
Indicates an action in which an entity comes down to and makes contact with a surface or ground, typically concluding a movement through air or space.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.