Triple

T4736606
Position Surface form Disambiguated ID Type / Status
Subject Greek mythology E105140 entity
Predicate hasHero P8706 FINISHED
Object Perseus E23577 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: Perseus | Statement: [Greek mythology, hasHero, Perseus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perseus
Context triple: [Greek mythology, hasHero, Perseus]
  • A. Perseus chosen
    Perseus is a legendary Greek hero famed for slaying the Gorgon Medusa and rescuing Andromeda.
  • B. Heracles
    Heracles is a legendary hero of Greek mythology renowned for his superhuman strength and his completion of the Twelve Labors.
  • C. Hippolyte
    Hippolyte is the given name of Hippolyte Fizeau, a 19th-century French physicist known for pioneering measurements of the speed of light.
  • D. Hercules Oetaeus
    Hercules Oetaeus is a Latin tragedy traditionally attributed to Seneca the Younger that dramatizes the death and apotheosis of the hero Hercules on Mount Oeta.
  • E. Erichthonius
    Erichthonius is a legendary early king of Dardania in Greek mythology, often regarded as an ancestor of the Trojan royal line.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64831c58819098758ac1f7839b3a completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a1796608190972865b2f6beef05 completed March 21, 2026, 6:26 a.m.
Created at: March 20, 2026, 1:19 p.m.