Triple

T24563158
Position Surface form Disambiguated ID Type / Status
Subject John III, Duke of Cleves E607710 entity
Predicate givenName P17 FINISHED
Object John
John III, Duke of Cleves, was a 16th-century German nobleman who ruled the Duchy of Cleves and was the father of Anne of Cleves, the fourth wife of King Henry VIII of England.
 E1644696 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: John | Statement: [John III, Duke of Cleves, givenName, John]
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: John
Triple: [John III, Duke of Cleves, givenName, John]
Generated description
John III, Duke of Cleves, was a 16th-century German nobleman who ruled the Duchy of Cleves and was the father of Anne of Cleves, the fourth wife of King Henry VIII of England.

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_69e2c4cc35a48190990b7571bc086df8 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f8a7488190a11f32014539a4a3 completed April 30, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10046efad0819094705d72f5becb6b completed May 22, 2026, 7:23 a.m.
NEDg Description generation batch_6a10078172348190af481658252dedee completed May 22, 2026, 7:36 a.m.
NED2 Entity disambiguation (via description) batch_6a10083cf1508190bd1bb8441d93c735 completed May 22, 2026, 7:39 a.m.
Created at: April 18, 2026, 2:28 a.m.