Triple
T36620718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir Tawil |
E904027
|
entity |
| Predicate | borderOrigin |
P201268
|
FINISHED |
| Object | colonial-era demarcations between Egypt and Anglo-Egyptian Sudan |
—
|
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: colonial-era demarcations between Egypt and Anglo-Egyptian Sudan | Statement: [Bir Tawil, borderOrigin, colonial-era demarcations between Egypt and Anglo-Egyptian Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderOrigin Context triple: [Bir Tawil, borderOrigin, colonial-era demarcations between Egypt and Anglo-Egyptian Sudan]
-
A.
borderStateOrigin
Indicates that a state shares a land or maritime border with the place where an entity originated.
-
B.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
C.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
D.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
| PDg | Predicate description generation | batch_69ffe22f453c81909867ee2d2047636f |
completed | May 10, 2026, 1:41 a.m. |
Created at: May 3, 2026, 4:11 p.m.