Triple

T1961320
Position Surface form Disambiguated ID Type / Status
Subject Yama E42391 entity
Predicate equivalent P3575 FINISHED
Object Yima E42391 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: Yima | Statement: [Yama, equivalent, Yima]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yima
Context triple: [Yama, equivalent, Yima]
  • A. Rishra
    Rishra is an industrial town and municipal area in the Hooghly district of West Bengal, India, known for its jute mills and proximity to Kolkata along the Hooghly River.
  • B. Nadym
    Nadym is a town in the Yamalo-Nenets Autonomous Okrug of Russia, known as a regional center for the natural gas industry and served by its own airport.
  • C. Yahi
    The Yahi were a small Native American group from northern California, known for being among the last surviving independent Indigenous peoples in the region and for the story of Ishi, their last known member.
  • D. Harauti
    Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
  • E. Yama chosen
    Yama is the Hindu god of death and justice, traditionally regarded as the ruler of the afterlife and judge of the souls of the dead.
  • 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_69a8870eea088190a38781990812a9bc completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb380bfc08190ae80f8e6570494b8 completed March 7, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbd133908190add1c78d91a813ef completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:36 p.m.