Triple

T24359731
Position Surface form Disambiguated ID Type / Status
Subject Hou Yi E614021 entity
Predicate employer P7 FINISHED
Object Emperor Yao
Emperor Yao is a legendary sage-king of ancient China, celebrated in Chinese mythology and history for his virtue, wisdom, and just rule during the era of the Three Sovereigns and Five Emperors.
E1632955 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: Emperor Yao | Statement: [Hou Yi, employer, Emperor Yao]
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: Emperor Yao
Triple: [Hou Yi, employer, Emperor Yao]
Generated description
Emperor Yao is a legendary sage-king of ancient China, celebrated in Chinese mythology and history for his virtue, wisdom, and just rule during the era of the Three Sovereigns and Five Emperors.

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_69e2d7dfe7f08190b7a1f3a36483ab05 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2934bcc608190b86bc091474bb259 completed April 29, 2026, 11:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fd66d89388190ab6083f90733c0da completed May 22, 2026, 4:07 a.m.
NEDg Description generation batch_6a0fd73ea7d88190b9bd774def308d97 completed May 22, 2026, 4:10 a.m.
NED2 Entity disambiguation (via description) batch_6a0fdb3919fc8190a66f585aff4e7570 completed May 22, 2026, 4:27 a.m.
Created at: April 18, 2026, 2 a.m.