Triple
T27607446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuzco |
E700218
|
entity |
| Predicate | roleInTheEmperor'sNewSchool |
P193526
|
FINISHED |
| Object | student emperor-in-training |
—
|
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: student emperor-in-training | Statement: [Kuzco, roleInTheEmperor'sNewSchool, student emperor-in-training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheEmperor'sNewSchool Context triple: [Kuzco, roleInTheEmperor'sNewSchool, student emperor-in-training]
-
A.
emperorRole
Indicates that an entity holds or fulfills the role, position, or office of an emperor in relation to another entity or context.
-
B.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
C.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
D.
finalEmperorOf
Indicates that one entity is the last ruler to hold the imperial title over another entity (such as a state, dynasty, or empire).
-
E.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
- F. None of above. chosen
Provenance (4 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 27, 2026, 2:10 p.m.