Triple

T26369160
Position Surface form Disambiguated ID Type / Status
Subject Eastern Jin dynasty E660723 entity
Predicate founder P104 FINISHED
Object Emperor Yuan of Jin
Emperor Yuan of Jin was the first emperor of the Eastern Jin dynasty, who reestablished Jin rule in southern China after the fall of the Western Jin.
E1731474 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 Yuan of Jin | Statement: [Eastern Jin dynasty, founder, Emperor Yuan of Jin]
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 Yuan of Jin
Triple: [Eastern Jin dynasty, founder, Emperor Yuan of Jin]
Generated description
Emperor Yuan of Jin was the first emperor of the Eastern Jin dynasty, who reestablished Jin rule in southern China after the fall of the Western Jin.

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_69ee812a698881908d6a58265995fa39 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6102ec7cc81909bca7ad00ab0dee0 completed May 2, 2026, 2:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c7fa19f081908de3613d0990f7e2 completed May 23, 2026, 3:30 p.m.
NEDg Description generation batch_6a11c97a0b8c8190930222a24b8ef5be completed May 23, 2026, 3:36 p.m.
NED2 Entity disambiguation (via description) batch_6a11ca61b1408190ab4bda33e53cb27c completed May 23, 2026, 3:40 p.m.
Created at: April 26, 2026, 10:57 p.m.