Triple
T7539846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Myth of Sisyphus |
E178245
|
entity |
| Predicate | usesMyth |
P60508
|
FINISHED |
| Object | Sisyphus eternally pushing a boulder uphill |
—
|
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: Sisyphus eternally pushing a boulder uphill | Statement: [The Myth of Sisyphus, usesMyth, Sisyphus eternally pushing a boulder uphill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMyth Context triple: [The Myth of Sisyphus, usesMyth, Sisyphus eternally pushing a boulder uphill]
-
A.
usesMythOf
chosen
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
B.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
C.
mythVariant
Indicates that one mythological narrative is a version, retelling, or alternative form of another myth.
-
D.
mythologized
Indicates that one entity has been turned into or treated as a mythic, legendary, or highly idealized figure or story by another.
-
E.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f873b17081908bb70aea0010d072 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.