Triple

T23220163
Position Surface form Disambiguated ID Type / Status
Subject Benalla E580864 entity
Predicate electorateFederal P9448 FINISHED
Object Indi 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: Indi | Statement: [Benalla, electorateFederal, Indi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indi
Context triple: [Benalla, electorateFederal, Indi]
  • A. Indi chosen
    Indi is an Australian federal electoral division in the state of Victoria, encompassing a largely rural and regional area in the state's northeast.
  • B. Indaial
    Indaial is a municipality in the state of Santa Catarina in southern Brazil, located in the Vale do Itajaí region and known for its industrial activity and German cultural heritage.
  • C. Mu Indi
    Mu Indi is a star in the constellation Indus, known as one of its designated Bayer stars.
  • D. Indienne
    Indienne was a French naval ship that took part in the early 19th-century Battle of the Basque Roads during the Napoleonic Wars.
  • E. Hindiyah
    Hindiyah is a town in Iraq, located in the Babil Governorate, known as the birthplace of former Prime Minister Nouri al-Maliki.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916870148190853874e6cf26bbc7 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.