Triple
T31977577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wedding feast of Pirithous |
E816488
|
entity |
| Predicate | timeInMythicCycle |
P20414
|
FINISHED |
| Object | age of heroes |
—
|
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: age of heroes | Statement: [wedding feast of Pirithous, timeInMythicCycle, age of heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInMythicCycle Context triple: [wedding feast of Pirithous, timeInMythicCycle, age of heroes]
-
A.
hasMythicTimeframe
Indicates that the relationship associates something with a timeframe situated in mythic or legendary, rather than historical, time.
-
B.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
C.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
D.
hasMythicMode
Indicates that an entity possesses or supports a special "mythic" difficulty or mode beyond standard levels.
-
E.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:11 a.m.