Triple
T36620654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir Tawil |
E904026
|
entity |
| Predicate | associatedBorderAgreement |
P166114
|
FINISHED |
| Object | 1899 Anglo-Egyptian Condominium Agreement |
E772358
|
NE 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: 1899 Anglo-Egyptian Condominium Agreement | Statement: [Bir Tawil, associatedBorderAgreement, 1899 Anglo-Egyptian Condominium Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBorderAgreement Context triple: [Bir Tawil, associatedBorderAgreement, 1899 Anglo-Egyptian Condominium Agreement]
-
A.
shareBorderAgreement
chosen
Indicates that two entities have a formally recognized agreement concerning their shared border.
-
B.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
C.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
- F. None of above.
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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20bf919081909761e5beacb663b0 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.