Triple
T34049208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Ethiopian Treaty of 1902 |
E873172
|
entity |
| Predicate | definesBoundaryWith |
P15022
|
FINISHED |
| Object | Anglo-Egyptian Sudan |
—
|
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: Anglo-Egyptian Sudan | Statement: [Anglo-Ethiopian Treaty of 1902, definesBoundaryWith, Anglo-Egyptian Sudan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesBoundaryWith Context triple: [Anglo-Ethiopian Treaty of 1902, definesBoundaryWith, Anglo-Egyptian Sudan]
-
A.
setsBoundary
chosen
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
B.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
C.
proposesBoundary
Indicates that one entity suggests or puts forward a specific boundary or limit to be considered or adopted in relation to another entity or context.
-
D.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
E.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:51 a.m.