Triple

T33783455
Position Surface form Disambiguated ID Type / Status
Subject Paradores de Turismo de España E865721 entity
Predicate hasPart P35 FINISHED
Object Parador de Ronda
Parador de Ronda is a historic luxury hotel dramatically perched on the edge of Ronda’s famous Tajo Gorge in Andalusia, Spain, offering panoramic views and refined accommodations.
E2073752 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: Parador de Ronda | Statement: [Paradores de Turismo de España, hasPart, Parador de Ronda]
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: Parador de Ronda
Triple: [Paradores de Turismo de España, hasPart, Parador de Ronda]
Generated description
Parador de Ronda is a historic luxury hotel dramatically perched on the edge of Ronda’s famous Tajo Gorge in Andalusia, Spain, offering panoramic views and refined accommodations.

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_69f3498ecc2c8190bcd85e3f11dc215e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fcca94808190839788575655878f completed May 3, 2026, 7:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a368228d8f88190a12ba98bf9a900a0 completed June 20, 2026, 12:06 p.m.
NEDg Description generation batch_6a36835ed2d48190b61bcf2d4e380945 completed June 20, 2026, 12:11 p.m.
NED2 Entity disambiguation (via description) batch_6a36848c2cd88190b28d40551392741b completed June 20, 2026, 12:16 p.m.
Created at: May 1, 2026, 1:45 a.m.