Triple
T11557300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules Furens |
E274048
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Lycus |
E71302
|
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: Lycus | Statement: [Hercules Furens, featuresCharacter, Lycus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lycus Context triple: [Hercules Furens, featuresCharacter, Lycus]
-
A.
Lycus
chosen
Lycus is a figure in Greek mythology, traditionally known as a son of the Pleiad Celaeno and the god Poseidon.
-
B.
Lycius
Lycius is the tragic mortal lover of the serpent-woman Lamia in John Keats’s narrative poem, whose doomed romance explores themes of illusion, love, and disillusionment.
-
C.
Lynceus
Lynceus is a figure in Greek mythology renowned as one of the Argonauts, famed for his exceptionally keen eyesight.
-
D.
Lykosoura
Lykosoura was an ancient Arcadian city in the Peloponnese, renowned as a major sanctuary site dedicated to the goddess Despoina in Greek religion.
-
E.
Eryx
Eryx is a figure in Greek mythology, a son of Aphrodite known as a powerful king and boxer associated with the city and region of Eryx in Sicily.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a888e8481909386009b9603e4d3 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6e87953088190b72d0afeb9251535 |
completed | April 21, 2026, 3:01 a.m. |
Created at: April 8, 2026, 9:37 p.m.