Triple
T6932585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huitzilopochtli |
E160470
|
entity |
| Predicate | pantheonRank |
P13203
|
FINISHED |
| Object | one of the principal Aztec 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: one of the principal Aztec gods | Statement: [Huitzilopochtli, pantheonRank, one of the principal Aztec gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pantheonRank Context triple: [Huitzilopochtli, pantheonRank, one of the principal Aztec gods]
-
A.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
B.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
pantheonIncludes
chosen
Indicates that a particular deity, figure, or entity is a member of, or belongs to, a specified pantheon.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
SSRank
Indicates a ranking relationship that orders entities based on their social status, standing, or relative importance within a specified context.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.