Triple

T35267901
Position Surface form Disambiguated ID Type / Status
Subject Luis Fernando de Orleans y Borbón E1018574 entity
Predicate givenName P17 FINISHED
Object Luis Fernando
Luis Fernando was a Spanish infante and member of the House of Bourbon-Orléans, known for his aristocratic lineage and turbulent personal life.
E2285556 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: Luis Fernando | Statement: [Luis Fernando de Orleans y Borbón, givenName, Luis Fernando]
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: Luis Fernando
Triple: [Luis Fernando de Orleans y Borbón, givenName, Luis Fernando]
Generated description
Luis Fernando was a Spanish infante and member of the House of Bourbon-Orléans, known for his aristocratic lineage and turbulent personal life.

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_69f76de4be5c8190a51705c07612cac8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f9b0e088190b1a338734e6d64e1 completed May 3, 2026, 6:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a45f963259c8190978fecff7351ea59 completed July 2, 2026, 5:38 a.m.
NEDg Description generation batch_6a45fa4cb24c8190933792aef1d93a8e completed July 2, 2026, 5:42 a.m.
NED2 Entity disambiguation (via description) batch_6a45fe7882748190874f9045670217b8 completed July 2, 2026, 6 a.m.
Created at: May 3, 2026, 4:02 p.m.