Triple
T11199757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibyl’s cave |
E265007
|
entity |
| Predicate | connectedWithMyth |
P9595
|
FINISHED |
| Object | Aeneas’s descent to the underworld |
—
|
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: Aeneas’s descent to the underworld | Statement: [Sibyl’s cave, connectedWithMyth, Aeneas’s descent to the underworld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedWithMyth Context triple: [Sibyl’s cave, connectedWithMyth, Aeneas’s descent to the underworld]
-
A.
coreMyth
Indicates that something constitutes a central, foundational myth within a belief system, narrative, or cultural tradition.
-
B.
usesMythOf
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
C.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
D.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
E.
mythVariant
Indicates that one mythological narrative is a version, retelling, or alternative form of another myth.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.