Triple

T5685447
Position Surface form Disambiguated ID Type / Status
Subject Katha Upanishad E125302 entity
Predicate primaryCharacter P9202 FINISHED
Object Yama 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: Yama | Statement: [Katha Upanishad, primaryCharacter, Yama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yama
Context triple: [Katha Upanishad, primaryCharacter, Yama]
  • A. 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.
  • B. Yamate
    Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
  • C. Sonamura
    Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
  • D. Yamadera
    Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
  • E. Dasuya
    Dasuya is a town and municipal council in the Hoshiarpur district of Punjab, India, known historically as a significant settlement in the region.
  • 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_69c0082a884c8190a79001bae658941f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c023ba52b48190b94f8a3ecff61eb4 completed March 22, 2026, 5:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a3d2b348190b44a067f485bca70 completed March 22, 2026, 9:08 p.m.
Created at: March 22, 2026, 3:44 p.m.