Triple
T5129216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phthia |
E115654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mythological region |
C6230
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mythological region Context triple: [Phthia, instanceOf, mythological region]
-
A.
mythological location
chosen
A mythological location is an imagined place rooted in folklore, religion, or legend, often imbued with supernatural qualities and symbolic meaning within a culture’s narrative tradition.
-
B.
mythological place
A mythological place is an imagined or legendary location rooted in cultural myths, folklore, or religious narratives, often embodying symbolic meanings, supernatural qualities, or moral themes rather than a verifiable physical existence.
-
C.
mythological concept
A mythological concept is an abstract idea, force, or principle originating in mythic narratives that helps explain the nature of the world, human experience, or the divine within a particular cultural tradition.
-
D.
mythological figure
A mythological figure is a legendary being or character from traditional stories and belief systems, often embodying cultural values, natural forces, or supernatural powers.
-
E.
mythological event
A mythological event is a significant occurrence within a culture’s traditional stories or legends, often involving gods, heroes, or supernatural forces that explain natural phenomena, origins, or moral truths.
- F. None of above.
Provenance (1 batch)
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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:42 p.m.