Triple
T34219138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia–Djibouti border |
E877875
|
entity |
| Predicate | hasBorderSecurityFor |
P145331
|
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, hasBorderSecurityFor, Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderSecurityFor Context triple: [Ethiopia–Djibouti border, hasBorderSecurityFor, Ethiopia]
-
A.
hasBorderGuardingMandateWith
Indicates that one entity has an official responsibility or mandate to guard, monitor, or secure a border in cooperation or association with another entity.
-
B.
hasBorderControlRole
Indicates that an entity holds a role or responsibility related to managing, enforcing, or overseeing border control activities.
-
C.
hasBorderSecurityImportance
Indicates that something holds significance or priority in the context of protecting and controlling a border.
-
D.
hasBorderControlBy
chosen
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
E.
hasBorderFacilityAccess
Indicates that an entity is permitted to enter, use, or operate within a designated border facility or checkpoint.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:55 a.m.