Triple

T36620690
Position Surface form Disambiguated ID Type / Status
Subject Bir Tawil E904027 entity
Predicate borderDefinitionIssue P105640 FINISHED
Object Egypt–Sudan border dispute 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 dispute | Statement: [Bir Tawil, borderDefinitionIssue, Egypt–Sudan border dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderDefinitionIssue
Context triple: [Bir Tawil, borderDefinitionIssue, Egypt–Sudan border dispute]
  • A. borderIssue chosen
    Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
  • B. borderDefinedBy
    Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
  • C. borderDefinedBetween
    Indicates that a boundary line or border is formally established between two geographic or political entities.
  • D. borderStraddling
    Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions 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_69f76e6ae750819096911e6e2d4d12c5 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffe12ee59c8190bc7da386e6d5332d completed May 10, 2026, 1:36 a.m.
PD Predicate disambiguation batch_69ffe0a138bc8190a3d4b48cd579e985 completed May 10, 2026, 1:34 a.m.
Created at: May 3, 2026, 4:11 p.m.