Triple

T16043904
Position Surface form Disambiguated ID Type / Status
Subject Badme region E389165 entity
Predicate hasAlternativeName P39 FINISHED
Object Badme area E389165 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: Badme area | Statement: [Badme region, hasAlternativeName, Badme area]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Badme area
Context triple: [Badme region, hasAlternativeName, Badme area]
  • A. Badme region chosen
    The Badme region is a disputed border area between Eritrea and Ethiopia that became a central flashpoint and symbolic focal point of the Eritrean–Ethiopian War.
  • B. Pankshin area
    Pankshin area is a locality in Plateau State, central Nigeria, known for its diverse ethnic groups and use of the Angas language.
  • C. Bansha area
    Bansha area is a rural locality and village community situated within County Tipperary in Ireland.
  • D. Tutuala area
    The Tutuala area is a coastal and forested region at the eastern tip of Timor-Leste known for its rugged cliffs, beaches, and cultural sites within Nino Konis Santana National Park.
  • E. Asni area
    The Asni area is a mountainous region in Morocco’s High Atlas known for its Berber villages, scenic valleys, and role as a gateway to nearby trekking and tourist destinations.
  • 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_69d86dae698881908327ef2d67706cb9 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1835c5bd48190b5b47379bf51f84e completed April 17, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbd95d508190a21db435fb69f8d7 completed May 10, 2026, 1:14 a.m.
Created at: April 10, 2026, 4:56 a.m.