Triple

T27748416
Position Surface form Disambiguated ID Type / Status
Subject Herrera E702050 entity
Predicate derivedFromToponym P9174 FINISHED
Object Herrera de Alcántara
Herrera de Alcántara is a small municipality in the province of Cáceres, in the autonomous community of Extremadura in western Spain, near the border with Portugal.
E1789822 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: Herrera de Alcántara | Statement: [Herrera, derivedFromToponym, Herrera de Alcántara]
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: Herrera de Alcántara
Triple: [Herrera, derivedFromToponym, Herrera de Alcántara]
Generated description
Herrera de Alcántara is a small municipality in the province of Cáceres, in the autonomous community of Extremadura in western Spain, near the border with Portugal.

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_69ef6a53c7388190899baa6daf42301c completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f6371c6454819099f05f09d60a374c completed May 2, 2026, 5:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ecab3d088190a709ae9a99825391 completed May 24, 2026, 12:18 p.m.
NEDg Description generation batch_6a12ed49266881909fd55a7028ad6a1f completed May 24, 2026, 12:21 p.m.
NED2 Entity disambiguation (via description) batch_6a12ee215b4c8190aeef56575c0c0015 completed May 24, 2026, 12:25 p.m.
Created at: April 27, 2026, 4:18 p.m.