Triple
T4922342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myth of Pandora |
E110493
|
entity |
| Predicate | portraysZeusAs |
P9987
|
FINISHED |
| Object | instigator of the punishment |
—
|
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: instigator of the punishment | Statement: [Myth of Pandora, portraysZeusAs, instigator of the punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysZeusAs Context triple: [Myth of Pandora, portraysZeusAs, instigator of the punishment]
-
A.
portraysPurushaAs
Indicates that one entity represents or depicts another entity as Purusha, the cosmic or primordial being.
-
B.
rankAmongWivesOfZeus
Indicates the relative hierarchical or ordinal position a wife holds among all the wives of Zeus.
-
C.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
D.
spouseAfterZeus
Indicates that one entity became a spouse of Zeus after a specified point or relative to another spouse in sequence.
-
E.
mythologicalRole
chosen
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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.