Triple
T19317399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec nobility |
E483133
|
entity |
| Predicate | legitimizedPowerThrough |
P19049
|
FINISHED |
| Object | mythic ancestry |
—
|
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: mythic ancestry | Statement: [Aztec nobility, legitimizedPowerThrough, mythic ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legitimizedPowerThrough Context triple: [Aztec nobility, legitimizedPowerThrough, mythic ancestry]
-
A.
legitimizedBy
Indicates that something gains legal, formal, or social validity as a result of the authority, action, or endorsement of another entity.
-
B.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
C.
usesPoliticalPowerFor
Indicates that an entity employs its political authority or influence to achieve, support, or advance a specified purpose, goal, or outcome.
-
D.
helpedLegitimize
chosen
Indicates that one entity’s actions or support contributed to making another entity appear more credible, acceptable, or officially recognized.
-
E.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given 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_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.