Triple

T35243659
Position Surface form Disambiguated ID Type / Status
Subject Zúñiga E1017597 entity
Predicate hasNotableBearer P458 FINISHED
Object Jorge de Zúñiga
Jorge de Zúñiga is a notable bearer of the Spanish surname Zúñiga, associated with a historically prominent Iberian noble lineage.
E2144079 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: Jorge de Zúñiga | Statement: [Zúñiga, hasNotableBearer, Jorge de Zúñiga]
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: Jorge de Zúñiga
Triple: [Zúñiga, hasNotableBearer, Jorge de Zúñiga]
Generated description
Jorge de Zúñiga is a notable bearer of the Spanish surname Zúñiga, associated with a historically prominent Iberian noble lineage.

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_69f76de235048190b990070c23c51b6b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f2858608190a39505e57736ef5a completed May 3, 2026, 6:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a384a1969d88190a9e4d62046c9d62b completed June 21, 2026, 8:31 p.m.
NEDg Description generation batch_6a384b8ec5548190b6b965f18269d962 completed June 21, 2026, 8:37 p.m.
NED2 Entity disambiguation (via description) batch_6a384be898d48190a89bc45464ff3964 completed June 21, 2026, 8:39 p.m.
Created at: May 3, 2026, 4:02 p.m.