Triple

T21449292
Position Surface form Disambiguated ID Type / Status
Subject Shaun Sipos E529165 entity
Predicate notableWork P4 FINISHED
Object Krypton NE NERFINISHED

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: Krypton | Statement: [Shaun Sipos, notableWork, Krypton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krypton
Context triple: [Shaun Sipos, notableWork, Krypton]
  • A. Krypton chosen
    Krypton is a television series set in the DC Comics universe that explores Superman’s home planet and ancestry before its destruction.
  • B. Mondas
    Mondas is the fictional twin planet of Earth in the Doctor Who universe, known as the original home of the Cybermen.
  • C. Vulcan
    Vulcan is an active stratovolcano located near Rabaul in East New Britain Province, Papua New Guinea, known for its explosive eruptions, including the major 1994 event.
  • D. Vulcan
    Vulcan is the Roman god of fire, metalworking, and the forge, often depicted as a blacksmith crafting weapons and armor for the gods.
  • E. Vulcan
    Vulcan is a small town in southern Alberta, Canada, best known for embracing a Star Trek theme that attracts science fiction fans and tourists.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c457579481909db68053ed99750c completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9d11ca48190aafe25c97dfa5578 completed April 23, 2026, 9:43 a.m.
Created at: April 16, 2026, 6:06 p.m.