Triple
T26240455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huey Tozoztli |
E656296
|
entity |
| Predicate | mainRitualFocus |
P111635
|
FINISHED |
| Object | maize cultivation |
—
|
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: maize cultivation | Statement: [Huey Tozoztli, mainRitualFocus, maize cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRitualFocus Context triple: [Huey Tozoztli, mainRitualFocus, maize cultivation]
-
A.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
-
B.
ritualCentersOn
chosen
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
C.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
D.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
E.
mainRitualTime
Indicates the time at which the primary or central ritual is performed.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8e81548190be9ff4ab11414a49 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 9:03 p.m.