Triple
T3027876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronis |
E82822
|
entity |
| Predicate | child |
P120
|
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: [Coronis, child, Asclepius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asclepius Context triple: [Coronis, child, 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.
Dorotheus
Dorotheus was a 6th-century Byzantine jurist who helped systematize and codify Roman law under Emperor Justinian I.
-
D.
Dorotheus
Dorotheus is a relatively obscure historical or religious figure known primarily through their association with Theophilus.
-
E.
Demophon
Demophon is a figure in Greek mythology, traditionally known as one of the sons of the Athenian hero Theseus and later a king of Athens.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abea8f4819090554d7319778170 |
completed | March 8, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f86995c88190bdf3af6f96f7a195 |
completed | March 11, 2026, 11:19 p.m. |
Created at: March 8, 2026, 3 p.m.