Triple
T37867628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Río Darro |
E944517
|
entity |
| Predicate | relevanciaTurística |
P7889
|
FINISHED |
| Object | elevada en Granada |
—
|
LITERAL 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: elevada en Granada | Statement: [Río Darro, relevanciaTurística, elevada en Granada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevanciaTurística Context triple: [Río Darro, relevanciaTurística, elevada en Granada]
-
A.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
B.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
C.
tourismImportance
chosen
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
D.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a tour.
-
E.
hasTourismPotential
Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
- F. None of above.
Provenance (3 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.