Triple
T32618966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ymir (Marvel Comics) |
E833867
|
entity |
| Predicate | mythos |
P137609
|
FINISHED |
| Object | Norse-inspired Marvel mythos |
—
|
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: Norse-inspired Marvel mythos | Statement: [Ymir (Marvel Comics), mythos, Norse-inspired Marvel mythos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythos Context triple: [Ymir (Marvel Comics), mythos, Norse-inspired Marvel mythos]
-
A.
μύθος
Indicates that one entity is a myth, story, or fable associated with another entity.
-
B.
mythologicalContent
chosen
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
mythologized
Indicates that one entity has been turned into or treated as a mythic, legendary, or highly idealized figure or story by another.
-
D.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
E.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.