Triple
T34012487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Islands mythology |
E872150
|
entity |
| Predicate | includesDeitiesType |
P205278
|
FINISHED |
| Object | creator gods |
—
|
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: creator gods | Statement: [Cook Islands mythology, includesDeitiesType, creator gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDeitiesType Context triple: [Cook Islands mythology, includesDeitiesType, creator gods]
-
A.
hasDeities
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
B.
sharesDeityTypesWith
Indicates that two entities are associated with at least one of the same types or categories of deities.
-
C.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
D.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
E.
includesMaleDeity
Indicates that the referenced set, group, or context contains at least one male deity as a member or participant.
- F. None of above. chosen
Provenance (4 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:51 a.m.