Triple
T7021330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurydice |
E162830
|
entity |
| Predicate | fateInMyth |
P3146
|
FINISHED |
| Object | returns permanently to the underworld when Orpheus looks back |
—
|
LITERAL 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: returns permanently to the underworld when Orpheus looks back | Statement: [Eurydice, fateInMyth, returns permanently to the underworld when Orpheus looks back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateInMyth Context triple: [Eurydice, fateInMyth, returns permanently to the underworld when Orpheus looks back]
-
A.
fate
chosen
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
knowledgeOfFate
Indicates that one entity is aware of or understands the destined or predetermined outcome concerning another entity or event.
-
C.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
D.
viewOnFate
Indicates a relationship where one entity holds a particular belief, attitude, or perspective about fate or predestination.
-
E.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
- F. None of above.
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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.