Triple
T11086406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egypt–Sudan border |
E262130
|
entity |
| Predicate | borderDisputeType |
P62867
|
FINISHED |
| Object | territorial dispute |
—
|
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: territorial dispute | Statement: [Egypt–Sudan border, borderDisputeType, territorial dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeType Context triple: [Egypt–Sudan border, borderDisputeType, territorial dispute]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
frontierDispute
Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
-
C.
associatedTerritoryDispute
chosen
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
D.
borderDemarcationTreaties
Indicates the existence of formal treaties that define, establish, or adjust the official boundary lines between two or more territories or jurisdictions.
-
E.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c3ed9c8190a3f5cdf1fe0e74a2 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.