Triple

T24519454
Position Surface form Disambiguated ID Type / Status
Subject Gaspar Méndez de Haro E606479 entity
Predicate familyName P18 FINISHED
Object Méndez de Haro
Méndez de Haro is a Spanish noble family name historically associated with influential statesmen and grandees of the Spanish Empire.
E606479 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: Méndez de Haro | Statement: [Gaspar Méndez de Haro, familyName, Méndez de Haro]
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: Méndez de Haro
Triple: [Gaspar Méndez de Haro, familyName, Méndez de Haro]
Generated description
Méndez de Haro is a Spanish noble family name historically associated with influential statesmen and grandees of the Spanish Empire.

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_69e2c4c85778819085f5da9af3569ad5 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a870e2c8819082b7c4d7197cd718 completed April 30, 2026, 12:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a118f71830481908b322a182efebb1b completed May 23, 2026, 11:28 a.m.
NEDg Description generation batch_6a118ff6c14081909cf07556b6ed9d08 completed May 23, 2026, 11:31 a.m.
NED2 Entity disambiguation (via description) batch_6a119076f8d0819083e4ee1dd938010d completed May 23, 2026, 11:33 a.m.
Created at: April 18, 2026, 2:24 a.m.