Triple

T7021375
Position Surface form Disambiguated ID Type / Status
Subject Argonauts E162831 entity
Predicate hasMember P10 FINISHED
Object Admetus E380385 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: Admetus | Statement: [Argonauts, hasMember, Admetus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Admetus
Context triple: [Argonauts, hasMember, Admetus]
  • A. Admetus chosen
    Admetus is a king in Greek mythology best known for being granted the chance to escape death through another’s sacrifice, a role famously linked with his devoted wife Alcestis.
  • B. Adrastus
    Adrastus is a legendary king of Argos in Greek mythology, best known as the leader of the Seven Against Thebes.
  • C. Deiphobus
    Deiphobus is a prince of Troy in Greek mythology, known as one of Priam's sons and a prominent warrior during the Trojan War.
  • D. Dagisthaeus
    Dagisthaeus was a 6th-century Byzantine general known for leading imperial forces during the Lazic War against the Sasanian Empire.
  • E. Rhadamanthus
    Rhadamanthus is a figure from Greek mythology renowned as a wise and just ruler who, after death, became one of the judges of the dead in the underworld.
  • 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_69c6885b26248190a857541e3d10e299 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1ec34a48190b64cafb94e2f8706 completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7757686bc819089f6749e43bbb89d completed March 28, 2026, 6:30 a.m.
Created at: March 27, 2026, 2:35 p.m.