Triple

T4906628
Position Surface form Disambiguated ID Type / Status
Subject Devas E109926 entity
Predicate associatedWith P37 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: [Devas, associatedWith, Yama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yama
Context triple: [Devas, associatedWith, 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. Dasuya
    Dasuya is a town and municipal council in the Hoshiarpur district of Punjab, India, known historically as a significant settlement in the region.
  • E. Ufenau
    Ufenau is a small, historically significant island in Lake Zurich, Switzerland, known for its preserved natural landscape and medieval church buildings.
  • 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_69bd441180708190ba42ffb44fea533a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e72ed5c819081104c99a398e0af completed March 20, 2026, 3:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69be89e3215081908120a8d307debbb3 completed March 21, 2026, 12:06 p.m.
Created at: March 20, 2026, 1:29 p.m.