Triple
T27790358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva de la Vaca |
E701060
|
entity |
| Predicate | nearbyAttractionCluster |
P181644
|
FINISHED |
| Object | San Gil extreme sports attractions |
—
|
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: San Gil extreme sports attractions | Statement: [Cueva de la Vaca, nearbyAttractionCluster, San Gil extreme sports attractions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAttractionCluster Context triple: [Cueva de la Vaca, nearbyAttractionCluster, San Gil extreme sports attractions]
-
A.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
-
B.
nearestTouristDestination
Indicates that one location is the closest tourist destination to another specified location.
-
C.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
nearbyActivityHub
chosen
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 5:27 p.m.