Triple

T16758140
Position Surface form Disambiguated ID Type / Status
Subject Battle of Badme E407263 entity
Predicate relatedPlace P3158 FINISHED
Object Badme E1191797 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 | Statement: [Battle of Badme, relatedPlace, Badme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Badme
Context triple: [Battle of Badme, relatedPlace, Badme]
  • A. Badme chosen
    Badme is a disputed border town between Ethiopia and Eritrea that became a focal point of their 1998–2000 war.
  • B. Palhaça
    Palhaça is a civil parish in the municipality of Oliveira do Bairro, located in Portugal’s Aveiro District.
  • C. Manmadhudu
    Manmadhudu is a popular 2002 Telugu romantic comedy film starring Nagarjuna Akkineni, known for its witty humor and charming portrayal of a commitment-phobic ad executive.
  • D. Bajool
    Bajool is a small rural locality in Central Queensland, Australia, situated south of Rockhampton and known for its agricultural surroundings and proximity to transport routes.
  • E. Manmad
    Manmad is a major railway and commercial town in Maharashtra, India, known as an important junction connecting several key routes in the region.
  • 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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3abea156c8190a5ee6d0028471810 completed April 18, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00aaf588bc8190adcc512eaa8d91e8 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:21 a.m.