Triple
T34072113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tongan mythology |
E873800
|
entity |
| Predicate | includesMythType |
P9998
|
FINISHED |
| Object | creation myth |
—
|
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: creation myth | Statement: [Tongan mythology, includesMythType, creation myth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMythType Context triple: [Tongan mythology, includesMythType, creation myth]
-
A.
hasMythType
chosen
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
B.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
C.
hasMythologicalDomain
Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
-
D.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
-
E.
mythVariant
Indicates that one mythological narrative is a version, retelling, or alternative form of another myth.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.