Triple
T5432030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden throne of Hera |
E121517
|
entity |
| Predicate | belongsToMythCycle |
P5444
|
FINISHED |
| Object | myths of Hephaestus |
—
|
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: myths of Hephaestus | Statement: [golden throne of Hera, belongsToMythCycle, myths of Hephaestus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMythCycle Context triple: [golden throne of Hera, belongsToMythCycle, myths of Hephaestus]
-
A.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
hasMythSource
chosen
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
-
C.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
D.
usesMythOf
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.