Triple
T25119943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purépecha pantheon |
E629237
|
entity |
| Predicate | primaryFertilityDeity |
P85058
|
FINISHED |
| Object | Cuerauáperi |
—
|
NE NERFINISHED |
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: Cuerauáperi | Statement: [Purépecha pantheon, primaryFertilityDeity, Cuerauáperi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFertilityDeity Context triple: [Purépecha pantheon, primaryFertilityDeity, Cuerauáperi]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
hasLoveAndFertilityGoddess
Indicates that an entity is associated with or possesses a goddess who embodies both love and fertility.
-
C.
deityOrigin
Indicates that one entity is the source, creator, or originating cause of a deity or divine being.
-
D.
associatedGoddess
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
-
E.
deityCategory
chosen
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 18, 2026, 6:27 a.m.