Triple

T9865051
Position Surface form Disambiguated ID Type / Status
Subject Pluto E239810 entity
Predicate equivalentTo P6530 FINISHED
Object Hades E19357 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: Hades | Statement: [Pluto, equivalentTo, Hades]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hades
Context triple: [Pluto, equivalentTo, Hades]
  • A. Hades chosen
    Hades is the ancient Greek god of the underworld and the dead, ruling over the realm of the afterlife.
  • B. Hades Dai
    Hades Dai is a formidable antagonist in the wuxia film "Crouching Tiger, Hidden Dragon: Sword of Destiny," known for his ruthless ambition and martial prowess.
  • C. gates of Hades
    The gates of Hades are the mythological entrance to the Greek underworld, marking the boundary between the realm of the living and the dead.
  • D. Orcus
    Orcus is a Roman god of the underworld, associated with punishing oath-breakers and often identified with or as an aspect of Pluto.
  • E. Orcus
    Orcus is a large trans-Neptunian dwarf-planet candidate in the Kuiper Belt, often considered a "twin" of Pluto due to its similar size, orbit, and composition.
  • 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_69ca84e7506c819095cbde4ff16512bb completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3ba7f288190a15ebec2cc3112c4 completed April 2, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e44dc0b8819082294a479299814e completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:36 p.m.