Triple
T15730658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māui-taha |
E381335
|
entity |
| Predicate | hasMythologicalType |
P9998
|
FINISHED |
| Object | human-like figure |
—
|
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: human-like figure | Statement: [Māui-taha, hasMythologicalType, human-like figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalType Context triple: [Māui-taha, hasMythologicalType, human-like figure]
-
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.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
D.
hasMythologicalBearer
Indicates that something is associated with, carried by, or represented by a figure from mythology.
-
E.
hasMythologicalNamesake
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb61cb881908b158609c1ccfa1e |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.