Triple
T8143101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hekademos |
E190142
|
entity |
| Predicate | hasVariantName |
P457
|
FINISHED |
| Object | Hecademus |
E712302
|
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: Hecademus | Statement: [Hekademos, hasVariantName, Hecademus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hecademus Context triple: [Hekademos, hasVariantName, Hecademus]
-
A.
Hecademus
chosen
Hecademus is an alternate name for Akademos, the legendary Athenian hero associated with the grove that later became Plato’s Academy.
-
B.
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.
-
C.
Deimachus
Deimachus is a relatively obscure figure in Greek mythology known primarily as the son of Enarete.
-
D.
Aristodemus
Aristodemus is a figure in Greek mythology, one of the Heracleidae and a descendant of Heracles associated with the legendary return of his lineage to the Peloponnese.
-
E.
Aristodemus
Aristodemus is a minor figure in ancient Greek philosophy, known primarily as a participant and narrator in Plato’s dialogue Symposium.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4444bb248190beaaa2ce4b8f3eaa |
completed | March 31, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cced2bba08819080c4a2bb8c9ba1f2 |
completed | April 1, 2026, 10:02 a.m. |
Created at: March 30, 2026, 5:36 p.m.