Triple
T20226007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Moctezuma de Tultengo |
E495380
|
entity |
| Predicate | ethnicOriginOfLine |
P194
|
FINISHED |
| Object | indigenous Nahua (Aztec) |
—
|
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: indigenous Nahua (Aztec) | Statement: [Dukes of Moctezuma de Tultengo, ethnicOriginOfLine, indigenous Nahua (Aztec)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOriginOfLine Context triple: [Dukes of Moctezuma de Tultengo, ethnicOriginOfLine, indigenous Nahua (Aztec)]
-
A.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
-
C.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
D.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
-
E.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd9c1f4819092a98f5fa84fb795 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.