Triple
T2282597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonautica |
E51313
|
entity |
| Predicate | featuresHero |
P36250
|
FINISHED |
| Object | Orpheus |
E31875
|
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: Orpheus | Statement: [Argonautica, featuresHero, Orpheus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orpheus Context triple: [Argonautica, featuresHero, Orpheus]
-
A.
Orpheus
chosen
Orpheus is a legendary musician, poet, and prophet in ancient Greek mythology, famed for his enchanting music that could charm all living things and even the gods of the underworld.
-
B.
Orfeo
Orfeo is a classical music record label known for its high-quality recordings of orchestral, operatic, and chamber music.
-
C.
Eurydice
Eurydice is a figure from Greek mythology best known as the wife of Orpheus, whose tragic death and attempted rescue from the underworld form one of the most famous mythic love stories.
-
D.
Philomelus
Philomelus was a Phocian military leader who initiated and led the early phases of the Third Sacred War in ancient Greece.
-
E.
Philomelus
Philomelus is a minor figure in Greek mythology known primarily as a son of the goddess Demeter.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc5b3d4988190bceb3dffa9734f4b |
completed | March 7, 2026, 6:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71e8f7488190ab0c0c93910984fa |
completed | March 9, 2026, 7:08 a.m. |
Created at: March 4, 2026, 7:48 p.m.