Triple

T32594057
Position Surface form Disambiguated ID Type / Status
Subject Trần Cảnh E833149 entity
Predicate father P120 FINISHED
Object Trần Thừa
Trần Thừa was a prominent Vietnamese nobleman and regent of the early Trần dynasty, best known as the father of Emperor Trần Thái Tông (Trần Cảnh) and a key architect of the dynasty’s rise to power.
E2016051 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: Trần Thừa | Statement: [Trần Cảnh, father, Trần Thừa]
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: Trần Thừa
Triple: [Trần Cảnh, father, Trần Thừa]
Generated description
Trần Thừa was a prominent Vietnamese nobleman and regent of the early Trần dynasty, best known as the father of Emperor Trần Thái Tông (Trần Cảnh) and a key architect of the dynasty’s rise to power.

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_69f34929ff648190aded9424aa7564ae completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c693fbfc8190ac7a90914510e2d7 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a349297413c8190be19da7378cadf26 completed June 19, 2026, 12:51 a.m.
NEDg Description generation batch_6a349371b8d88190a2c08921c9b35d27 completed June 19, 2026, 12:55 a.m.
NED2 Entity disambiguation (via description) batch_6a3493e81ad88190825bbd5b0be3800c completed June 19, 2026, 12:57 a.m.
Created at: May 1, 2026, 1:05 a.m.