Triple
T20286027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Legends |
E509876
|
entity |
| Predicate | hasMythicMode |
P139545
|
FINISHED |
| Object | modern myth-making |
—
|
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: modern myth-making | Statement: [Two Legends, hasMythicMode, modern myth-making]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythicMode Context triple: [Two Legends, hasMythicMode, modern myth-making]
-
A.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
B.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
C.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
D.
hasMythicFunction
Indicates that something serves a symbolic, narrative, or ritual role within a mythic or mythological framework.
-
E.
hasMythicFounder
Indicates that an entity is traditionally believed to have been founded or established by a legendary or mythological figure rather than a historically verified person.
- F. None of above. chosen
Provenance (4 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e676924f48819095f6224c8d9bb257 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:06 a.m.