Triple

T32342906
Position Surface form Disambiguated ID Type / Status
Subject Sanabria E826367 entity
Predicate hasMajorTown P316 FINISHED
Object Puebla de Sanabria
Puebla de Sanabria is a historic fortified town in the province of Zamora, Spain, known for its medieval castle and role as the main urban center of the Sanabria region.
E2068611 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: Puebla de Sanabria | Statement: [Sanabria, hasMajorTown, Puebla de Sanabria]
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: Puebla de Sanabria
Triple: [Sanabria, hasMajorTown, Puebla de Sanabria]
Generated description
Puebla de Sanabria is a historic fortified town in the province of Zamora, Spain, known for its medieval castle and role as the main urban center of the Sanabria region.

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_69f34914dfc48190a390cd0720d9e86f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6be275fa08190b656651a4e27f7aa completed May 3, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a366e7524d081908f5838eab8a7b79e completed June 20, 2026, 10:41 a.m.
NEDg Description generation batch_6a366eef61b88190b26895e9ad436bec completed June 20, 2026, 10:43 a.m.
NED2 Entity disambiguation (via description) batch_6a366f8d319481909dba4d6b34c5313e completed June 20, 2026, 10:46 a.m.
Created at: May 1, 2026, 12:48 a.m.