Triple

T4976665
Position Surface form Disambiguated ID Type / Status
Subject gon E111781 entity
Predicate hasAlternativeName P39 FINISHED
Object Gondi E20268 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: Gondi | Statement: [gon, hasAlternativeName, Gondi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gondi
Context triple: [gon, hasAlternativeName, Gondi]
  • A. Gondi chosen
    Gondi is a Dravidian language spoken primarily by the Gondi people in central India, especially across parts of Madhya Pradesh, Maharashtra, Chhattisgarh, and neighboring regions.
  • B. Gotō
    Gotō is a Japanese surname borne by various notable figures in politics, business, and the arts.
  • C. Oschiri
    Oschiri is a small town and comune in the Gallura region of northern Sardinia, Italy, known for its rural landscape and archaeological sites.
  • D. Takaishi
    Takaishi is a city in Osaka Prefecture, Japan, known as a small industrial and residential hub within the Osaka metropolitan area.
  • E. Gyoda
    Gyoda is a historic city in eastern Japan known for its ancient rice paddies, traditional tabi sock production, and preserved castle town atmosphere.
  • 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_69bd441adc208190b70a033a0741d01e completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7231448c8190a5d0a5135a9cfdf1 completed March 20, 2026, 4:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a0634b48190acb4a1834f5647cf completed March 21, 2026, 12:07 p.m.
Created at: March 20, 2026, 1:33 p.m.