Triple
T36620652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir Tawil |
E904026
|
entity |
| Predicate | nearBorderFeature |
P46305
|
FINISHED |
| Object | Egypt–Sudan border |
—
|
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: Egypt–Sudan border | Statement: [Bir Tawil, nearBorderFeature, Egypt–Sudan border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearBorderFeature Context triple: [Bir Tawil, nearBorderFeature, Egypt–Sudan border]
-
A.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
B.
nearStateBorderWith
Indicates that one entity is located close to the state border shared with another specified state or region.
-
C.
nearBorderDirection
Indicates that one entity is located close to a border or boundary in a specified directional orientation relative to that border.
-
D.
nearInternationalBoundary
chosen
Indicates that one entity is located close to an international boundary separating two or more countries.
-
E.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:11 p.m.