Triple

T7226030
Position Surface form Disambiguated ID Type / Status
Subject Rod of Asclepius E154780 entity
Predicate namedAfter P63 FINISHED
Object Asclepius E28749 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: Asclepius | Statement: [Rod of Asclepius, namedAfter, Asclepius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asclepius
Context triple: [Rod of Asclepius, namedAfter, Asclepius]
  • A. Asclepius chosen
    Asclepius is the ancient Greek god of medicine and healing, revered for his ability to cure illness and restore health.
  • B. Calchas
    Calchas is a prophetic Trojan priest who defects to the Greeks in medieval and classical tales of the Trojan War, including Chaucer’s "Troilus and Criseyde."
  • C. Ascalaphe
    Ascalaphe is a minor figure in Greek mythology, known as the informer who revealed Persephone’s eating of pomegranate seeds and was punished by being transformed into an owl.
  • D. Dorotheus
    Dorotheus was a 6th-century Byzantine jurist who helped systematize and codify Roman law under Emperor Justinian I.
  • E. Dorotheus
    Dorotheus is a relatively obscure historical or religious figure known primarily through their association with Theophilus.
  • 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_69c68811dd1c8190ac460bb39e64e1f0 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6e9de21e081908f30700f6211c5ef completed March 27, 2026, 8:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802a61718819088cc2d37818af4ca completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 2:54 p.m.