Triple
T29564940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomerans |
E753137
|
entity |
| Predicate | tourismRelatedActivity |
P1769
|
FINISHED |
| Object | rural tourism |
—
|
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: rural tourism | Statement: [Gomerans, tourismRelatedActivity, rural tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismRelatedActivity Context triple: [Gomerans, tourismRelatedActivity, rural tourism]
-
A.
tourismEvent
Indicates an event or activity that is organized for or significantly involves tourism, attracting visitors for leisure, cultural, or recreational purposes.
-
B.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
D.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
-
E.
tourismService
Indicates a relationship where an entity provides or is associated with services intended for tourists, such as travel, accommodation, or guided activities.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d2061c88190b433ce83fa06d41b |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:51 p.m.