Triple

T20170614
Position Surface form Disambiguated ID Type / Status
Subject East Nimar E491947 entity
Predicate containsTown P847 FINISHED
Object Mundi 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: Mundi | Statement: [East Nimar, containsTown, Mundi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mundi
Context triple: [East Nimar, containsTown, Mundi]
  • A. Mundi chosen
    Mundi is a town in the Khandwa district of Madhya Pradesh, India, known locally as an important regional center for trade and agriculture.
  • B. Mundo
    Mundo is a Spanish given name commonly used as a shortened or affectionate form of longer names such as Raimundo.
  • C. Mulk
    Mulk is the name of one of the nineteen months in the Badíʻ (Baháʼí) calendar, associated with the concept of dominion or sovereignty.
  • D. Terrasur
    Terrasur is a Chilean intercity passenger rail service operated under the state-owned railway company Empresa de los Ferrocarriles del Estado (EFE).
  • E. Mund
    Mund is a small Swiss village and former municipality in the canton of Valais, known for its traditional alpine character and saffron cultivation.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66847ed9481908e6b23b399fa7005 completed April 20, 2026, 5:54 p.m.
Created at: April 11, 2026, 11:35 p.m.