Triple

T4519630
Position Surface form Disambiguated ID Type / Status
Subject Ashvins E103233 entity
Predicate siblingOf P363 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: [Ashvins, siblingOf, Yama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yama
Context triple: [Ashvins, siblingOf, 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. Ufenau
    Ufenau is a small, historically significant island in Lake Zurich, Switzerland, known for its preserved natural landscape and medieval church buildings.
  • E. Moruya
    Moruya is a coastal town in New South Wales, Australia, known for its scenic river setting, nearby beaches, and historic granite quarries.
  • 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_69bd43dba59881908cf59b31df8c7ae1 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5747e90c81908fa112ecace699a9 completed March 20, 2026, 2:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb90b785c81909e76469819f3a487 completed March 20, 2026, 9:15 p.m.
Created at: March 20, 2026, 1:02 p.m.