Triple
T19317388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec nobility |
E483133
|
entity |
| Predicate | trainedTheirChildrenIn |
P40765
|
FINISHED |
| Object | calmecac |
—
|
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: calmecac | Statement: [Aztec nobility, trainedTheirChildrenIn, calmecac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainedTheirChildrenIn Context triple: [Aztec nobility, trainedTheirChildrenIn, calmecac]
-
A.
children
Indicates that one entity is the offspring or direct descendant of another entity.
-
B.
sonRaisedIn
Indicates that a son spent his childhood or formative years being brought up in a particular place or environment.
-
C.
trainedAs
Indicates that one entity has received education or instruction to perform the role, profession, or function represented by another entity.
-
D.
commonlyTrainedWith
Indicates that two entities are typically trained, practiced, or learned together as part of the same routine, curriculum, or skill set.
-
E.
providesTrainingFor
chosen
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d85046c81909d972a6b369b0c2b |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.