Triple

T28027892
Position Surface form Disambiguated ID Type / Status
Subject Jacques of Savoy, Duke of Nemours E708175 entity
Predicate father P120 FINISHED
Object Philip, Duke of Nemours
Philip, Duke of Nemours was a French nobleman of the House of Savoy who held the ducal title of Nemours in the 16th century.
E1821096 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: Philip, Duke of Nemours | Statement: [Jacques of Savoy, Duke of Nemours, father, Philip, Duke of Nemours]
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: Philip, Duke of Nemours
Triple: [Jacques of Savoy, Duke of Nemours, father, Philip, Duke of Nemours]
Generated description
Philip, Duke of Nemours was a French nobleman of the House of Savoy who held the ducal title of Nemours in the 16th century.

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_69ef9b6bdd9c8190bb3a574a03774ad1 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f63c6ef4348190821f991c682a6894 completed May 2, 2026, 6:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cac21a3ec8190af22da7009d0b73c completed May 31, 2026, 9:46 p.m.
NEDg Description generation batch_6a1cac85def4819098f74dc03bec290c completed May 31, 2026, 9:47 p.m.
NED2 Entity disambiguation (via description) batch_6a1cacd66ef481908a6fe331710f0677 completed May 31, 2026, 9:49 p.m.
Created at: April 27, 2026, 8:14 p.m.