Triple

T8847541
Position Surface form Disambiguated ID Type / Status
Subject Greater Khartoum metropolitan area E210543 entity
Predicate contains P35 FINISHED
Object Bahri E255452 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: Bahri | Statement: [Greater Khartoum metropolitan area, contains, Bahri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bahri
Context triple: [Greater Khartoum metropolitan area, contains, Bahri]
  • A. Bahri chosen
    Bahri is the commonly used Arabic name for Khartoum North, a major city forming part of Sudan’s capital metropolitan area.
  • B. Baheri
    Baheri is a town located in the Darbhanga district of the Indian state of Bihar.
  • C. Meer
    Meer is a surname of South Asian origin borne by numerous individuals, including notable figures in politics, academia, and the arts.
  • D. Bahr
    Bahr is a German surname most notably associated with Egon Bahr, a key architect of West Germany’s Ostpolitik during the Cold War.
  • E. Haliç
    Haliç is the Turkish name for the Golden Horn, the historic estuary that forms a natural harbor and inlet of the Bosphorus in Istanbul.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca838967bc8190b46c3c80a2887ea4 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60a9194c8190bdfefc55a8fb29a3 completed April 1, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf89bd3ef48190a6a2efff18db4dbd completed April 3, 2026, 9:34 a.m.
Created at: March 30, 2026, 6:49 p.m.