Triple
T31706289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moana universe |
E809188
|
entity |
| Predicate | includesMythologicalElement |
P137609
|
FINISHED |
| Object | demigods |
—
|
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: demigods | Statement: [Moana universe, includesMythologicalElement, demigods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMythologicalElement Context triple: [Moana universe, includesMythologicalElement, demigods]
-
A.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
B.
mythologicalContent
chosen
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
hasMythologicalUsage
Indicates that something is used, referenced, or functions within a mythological context or tradition.
-
D.
hasMythologicalInhabitant
Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
-
E.
mythologicalTextMention
Indicates that a mythological text mentions, references, or otherwise explicitly refers to a given entity or concept.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: April 30, 2026, 11:14 p.m.