Triple

T27310100
Position Surface form Disambiguated ID Type / Status
Subject Louis Alexandre de Bourbon E689179 entity
Predicate alsoKnownAs P39 FINISHED
Object comte de Toulouse
The comte de Toulouse was a legitimized son of King Louis XIV of France who became a prominent naval commander and high-ranking noble during the late 17th and early 18th centuries.
E1766317 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: comte de Toulouse | Statement: [Louis Alexandre de Bourbon, alsoKnownAs, comte de Toulouse]
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: comte de Toulouse
Triple: [Louis Alexandre de Bourbon, alsoKnownAs, comte de Toulouse]
Generated description
The comte de Toulouse was a legitimized son of King Louis XIV of France who became a prominent naval commander and high-ranking noble during the late 17th and early 18th centuries.

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_69ef355b931c8190a63cafaf7bcc008b completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f627b24dd48190a6192153354240ca completed May 2, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a129cb2fb788190aaaecddaacc72280 completed May 24, 2026, 6:37 a.m.
NEDg Description generation batch_6a129e256d0c8190874e54b63227ce0a completed May 24, 2026, 6:43 a.m.
NED2 Entity disambiguation (via description) batch_6a129ebbbf288190afbb4f21249a6fcf completed May 24, 2026, 6:46 a.m.
Created at: April 27, 2026, 11:27 a.m.