Triple

T1961322
Position Surface form Disambiguated ID Type / Status
Subject Yama E42391 entity
Predicate equivalent P3575 FINISHED
Object Enma 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: Enma | Statement: [Yama, equivalent, Enma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Enma
Context triple: [Yama, equivalent, Enma]
  • 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. Oya
    Oya is a powerful Yoruba orisha associated with storms, winds, transformation, and the Niger River.
  • C. Izanami
    Izanami is a primordial Japanese goddess in Shinto mythology, known as the creator of many islands and deities alongside her consort Izanagi and as a ruler of the land of the dead after her death.
  • D. 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.
  • E. Kushinadahime
    Kushinadahime is a goddess in Japanese mythology, best known as the rescued maiden whom the storm god Susanoo marries after saving her from the eight-headed serpent Yamata no Orochi.
  • 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.