Triple
T1396801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toltec civilization |
E30683
|
entity |
| Predicate | hasRulingTitle |
P17756
|
FINISHED |
| Object | tlatoani |
—
|
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: tlatoani | Statement: [Toltec civilization, hasRulingTitle, tlatoani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingTitle Context triple: [Toltec civilization, hasRulingTitle, tlatoani]
-
A.
hasRulerTitle
chosen
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
D.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
E.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3817320819093067b1444d70b74 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.