Triple

T24493545
Position Surface form Disambiguated ID Type / Status
Subject House of Tupou E617712 entity
Predicate hasHeirApparent P2940 FINISHED
Object Crown Prince Tupoutoʻa ʻUlukalala
Crown Prince Tupoutoʻa ʻUlukalala is the heir apparent to the Tongan throne and a senior member of the Tongan royal family.
E1670402 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: Crown Prince Tupoutoʻa ʻUlukalala | Statement: [House of Tupou, hasHeirApparent, Crown Prince Tupoutoʻa ʻUlukalala]
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: Crown Prince Tupoutoʻa ʻUlukalala
Triple: [House of Tupou, hasHeirApparent, Crown Prince Tupoutoʻa ʻUlukalala]
Generated description
Crown Prince Tupoutoʻa ʻUlukalala is the heir apparent to the Tongan throne and a senior member of the Tongan royal family.

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_69e2d7f4e6bc8190aec540ae3b9ed7f2 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2a6e24c2c8190875bd0bfed2bf28d completed April 30, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a106794e7cc8190a1b3f8ff52d47e54 completed May 22, 2026, 2:26 p.m.
NEDg Description generation batch_6a106907472881908bb4565bb581dbbd completed May 22, 2026, 2:32 p.m.
NED2 Entity disambiguation (via description) batch_6a10697c10bc8190a984f68d0bce5078 completed May 22, 2026, 2:34 p.m.
Created at: April 18, 2026, 2:22 a.m.