Triple

T24130296
Position Surface form Disambiguated ID Type / Status
Subject Charles de Bourbon, Duke of Vendôme E597931 entity
Predicate title P38 FINISHED
Object Count of Vendôme
The Count of Vendôme was a French noble title historically associated with the influential Bourbon-Vendôme branch of the House of Bourbon.
E1621221 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: Count of Vendôme | Statement: [Charles de Bourbon, Duke of Vendôme, title, Count of Vendôme]
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: Count of Vendôme
Triple: [Charles de Bourbon, Duke of Vendôme, title, Count of Vendôme]
Generated description
The Count of Vendôme was a French noble title historically associated with the influential Bourbon-Vendôme branch of the House of Bourbon.

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_69e288c808b881909fed7d18f04bcbbe completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1df7644808190b4bbbf4db1539f48 completed April 29, 2026, 10:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fad1db8d48190810d1b2b2981a340 completed May 22, 2026, 1:10 a.m.
NEDg Description generation batch_6a0fae2d71448190b191a4877c698840 completed May 22, 2026, 1:15 a.m.
NED2 Entity disambiguation (via description) batch_6a0faf073c088190bbf21e4dd0434fc1 completed May 22, 2026, 1:19 a.m.
Created at: April 17, 2026, 11:24 p.m.