Triple
T27790345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva de la Vaca |
E701060
|
entity |
| Predicate | nearbyActivityHub |
P181644
|
FINISHED |
| Object | San Gil adventure tourism area |
—
|
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 adventure tourism area | Statement: [Cueva de la Vaca, nearbyActivityHub, San Gil adventure tourism area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyActivityHub Context triple: [Cueva de la Vaca, nearbyActivityHub, San Gil adventure tourism area]
-
A.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
B.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
C.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
D.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
E.
nearbyEconomicActivity
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
- F. None of above. chosen
Provenance (4 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 27, 2026, 5:27 p.m.