Triple
T15712340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori mythology |
E380868
|
entity |
| Predicate | hasDomainDeity |
P45989
|
FINISHED |
| Object | Tāne Mahuta – forests and birds |
—
|
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: Tāne Mahuta – forests and birds | Statement: [Māori mythology, hasDomainDeity, Tāne Mahuta – forests and birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainDeity Context triple: [Māori mythology, hasDomainDeity, Tāne Mahuta – forests and birds]
-
A.
deityDomain
Indicates that a deity has authority, influence, or primary association over a particular domain, aspect, or sphere of existence.
-
B.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
hasComponentDeity
chosen
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
D.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
E.
hasGuardianDeity
Indicates that an entity is under the protection or patronage of a specific guardian deity.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f8f5d6081908243fa59b46b7c76 |
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:45 a.m.