Triple

T32342916
Position Surface form Disambiguated ID Type / Status
Subject Sanabria E826367 entity
Predicate hasMajorTown P316 FINISHED
Object Rosinos de la Requejada
Rosinos de la Requejada is a small municipality in the Sanabria region of the province of Zamora, in the autonomous community of Castile and León, Spain.
E2002044 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: Rosinos de la Requejada | Statement: [Sanabria, hasMajorTown, Rosinos de la Requejada]
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: Rosinos de la Requejada
Triple: [Sanabria, hasMajorTown, Rosinos de la Requejada]
Generated description
Rosinos de la Requejada is a small municipality in the Sanabria region of the province of Zamora, in the autonomous community of Castile and León, Spain.

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_6a30572fc9508190a3ad84c9a96e2de8 completed June 15, 2026, 7:49 p.m.
NEDg Description generation batch_6a3058ccffe881908c62d79b38ee66b6 completed June 15, 2026, 7:55 p.m.
NED2 Entity disambiguation (via description) batch_6a30596f48748190b74f411b230f68a9 completed June 15, 2026, 7:58 p.m.
Created at: May 1, 2026, 12:48 a.m.