Triple
T34071000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akobo border crossing |
E873767
|
entity |
| Predicate | borderControlPresence |
P121973
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Akobo border crossing, borderControlPresence, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderControlPresence Context triple: [Akobo border crossing, borderControlPresence, limited]
-
A.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
B.
borderControlMeasure
chosen
Indicates a policy or action implemented to regulate, monitor, or restrict the movement of people or goods across a border.
-
C.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
D.
borderControlRelevance
Indicates the extent to which something is pertinent or applicable to border control activities, policies, or decisions.
-
E.
borderControlDirection
Indicates the direction in which border control procedures are applied or enforced between two locations or jurisdictions.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 1, 2026, 1:52 a.m.