Triple

T7306467
Position Surface form Disambiguated ID Type / Status
Subject Ho E167986 entity
Predicate language P15 FINISHED
Object Ho language E199648 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: Ho language | Statement: [Ho, language, Ho language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ho language
Context triple: [Ho, language, Ho language]
  • A. Ho language chosen
    Ho language is an Austroasiatic language of the Munda family spoken primarily by the Ho people in eastern India, particularly in Jharkhand and Odisha.
  • B. Ha language
    Ha language is a Bantu language spoken primarily by the Ha people in western Tanzania, particularly around the shores of Lake Tanganyika.
  • C. Hu language
    Hu language is a variety of Wu Chinese spoken primarily in and around Shanghai, known for its distinct phonology and vocabulary compared to Standard Mandarin.
  • D. Hoava language
    The Hoava language is an Oceanic language spoken by communities in the western Solomon Islands, particularly on New Georgia Island.
  • E. Mon language
    Mon language is an Austroasiatic language historically spoken in parts of Myanmar and Thailand, notable for its ancient literary tradition and influence on regional scripts and cultures.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebd7dcf88190b3e66bea327fc63d completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e5603a288190a19d426905781cae completed March 28, 2026, 2:27 p.m.
Created at: March 27, 2026, 3:01 p.m.