Triple

T4736608
Position Surface form Disambiguated ID Type / Status
Subject Greek mythology E105140 entity
Predicate hasHero P8706 FINISHED
Object Achilles E31264 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: Achilles | Statement: [Greek mythology, hasHero, Achilles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Achilles
Context triple: [Greek mythology, hasHero, Achilles]
  • A. Achilles chosen
    Achilles is a legendary Greek hero of the Trojan War, famed for his near invincibility, martial prowess, and central role in Homer's Iliad.
  • B. Diomedon
    Diomedon was an Athenian naval commander during the Peloponnesian War, noted for his role in major late-war battles against Sparta.
  • C. Palamedes
    Palamedes is a 1625 Dutch tragedy by Joost van den Vondel that allegorically critiques political and religious injustice in the Dutch Republic.
  • D. Diomed
    Diomed was an 18th-century British Thoroughbred racehorse best known for winning the inaugural Epsom Derby and later becoming an influential sire in American bloodlines.
  • E. Diomedes
    Diomedes is a hero from Greek mythology, famed for his role in the Trojan War as one of the Achaeans’ greatest warriors and a favored ally of the goddess Athena.
  • 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_69be43ab20848190879de3a0d6366523 completed March 21, 2026, 7:07 a.m.
Created at: March 20, 2026, 1:19 p.m.