Triple

T31825690
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Avalor E812386 entity
Predicate hasRoyalAdvisor P172722 FINISHED
Object Chancellor Esteban
Chancellor Esteban is a prominent character in Disney's "Elena of Avalor," serving as the kingdom’s often self-serving but ultimately redeemable royal advisor.
E1980424 NE 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: Chancellor Esteban | Statement: [Kingdom of Avalor, hasRoyalAdvisor, Chancellor Esteban]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Chancellor Esteban
Triple: [Kingdom of Avalor, hasRoyalAdvisor, Chancellor Esteban]
Generated description
Chancellor Esteban is a prominent character in Disney's "Elena of Avalor," serving as the kingdom’s often self-serving but ultimately redeemable royal advisor.

Provenance (5 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_69f348e97fa48190aa06286962af6dee completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd55efc3788190ac0a1e530d347e4f completed May 8, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e659eba3881909e51cdc73614611b completed June 14, 2026, 8:26 a.m.
NEDg Description generation batch_6a2e6754a848819092c9658e0837fecd completed June 14, 2026, 8:33 a.m.
NED2 Entity disambiguation (via description) batch_6a2e698816ac81909f66c1323f766eaa completed June 14, 2026, 8:42 a.m.
Created at: April 30, 2026, 11:46 p.m.