Triple

T19659261
Position Surface form Disambiguated ID Type / Status
Subject Burao E472035 entity
Predicate roadConnection P385 FINISHED
Object Erigavo 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: Erigavo | Statement: [Burao, roadConnection, Erigavo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erigavo
Context triple: [Burao, roadConnection, Erigavo]
  • A. Erigavo chosen
    Erigavo is a major town and administrative center in the Sanaag region of northern Somalia, claimed by the self-declared Republic of Somaliland.
  • B. Erista
    Erista is the internal codename for Nvidia’s original Tegra X1 system-on-chip, notably used in the first-generation Nintendo Switch.
  • C. Egino
    Egino is a masculine given name of Germanic origin, historically borne by several medieval European nobles and clerics.
  • D. Eidagale
    Eidagale is a prominent subclan of the Isaaq clan-family in the Somali ethnic lineage, historically influential in the politics and trade of the Horn of Africa.
  • E. Ering
    Ering is a small municipality in Bavaria, Germany, located near the town of Simbach am Inn along the Austrian border.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51395348190ac1416d46dfc6db0 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e641485ce481908b3860fa5e3a9f6e completed April 20, 2026, 3:07 p.m.
Created at: April 10, 2026, 1:45 p.m.