Triple

T27848928
Position Surface form Disambiguated ID Type / Status
Subject Su E703897 entity
Predicate hasNotableBearer P458 FINISHED
Object Su Xun
Su Xun was a prominent Song dynasty Chinese writer and prose stylist, best known as the father of the famed literati Su Shi and Su Zhe and as one of the "Eight Great Prose Masters of the Tang and Song."
E1799251 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: Su Xun | Statement: [Su, hasNotableBearer, Su Xun]
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: Su Xun
Triple: [Su, hasNotableBearer, Su Xun]
Generated description
Su Xun was a prominent Song dynasty Chinese writer and prose stylist, best known as the father of the famed literati Su Shi and Su Zhe and as one of the "Eight Great Prose Masters of the Tang and Song."

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_69ef840d9e3c819093615ebff4ec22be completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f63902f71c8190b26ac186ad00acbf completed May 2, 2026, 5:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b87f36608190ae9143b0e6b73cad completed May 26, 2026, 3:13 p.m.
NEDg Description generation batch_6a15bb1f07c48190aaecc330abbba12f completed May 26, 2026, 3:24 p.m.
NED2 Entity disambiguation (via description) batch_6a15bbab614c81908b86ec6c4043e1d0 completed May 26, 2026, 3:26 p.m.
Created at: April 27, 2026, 6:09 p.m.