Triple
T33716189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahua religion |
E863878
|
entity |
| Predicate | hasPantheonType |
P98640
|
FINISHED |
| Object | polytheism |
—
|
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: polytheism | Statement: [Nahua religion, hasPantheonType, polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPantheonType Context triple: [Nahua religion, hasPantheonType, polytheism]
-
A.
hasPantheonName
Indicates that an entity is associated with a specific pantheon and is identified by the given pantheon name.
-
B.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
C.
hasPantheonStructure
chosen
Indicates that an entity possesses or is associated with a pantheon-like hierarchical structure, typically organizing multiple deities or divine figures.
-
D.
hasApotheosisType
Indicates the specific kind or form of apotheosis associated with an entity or event.
-
E.
includesPantheon
Indicates that one entity contains or encompasses a particular pantheon as part of its scope or composition.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:44 a.m.