Triple
T9224006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia de Monte Clérigo |
E221633
|
entity |
| Predicate | isPartOfTourismType |
P1769
|
FINISHED |
| Object | nature 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: nature tourism | Statement: [Praia de Monte Clérigo, isPartOfTourismType, nature tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTourismType Context triple: [Praia de Monte Clérigo, isPartOfTourismType, nature tourism]
-
A.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
B.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
C.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
D.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
E.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9c71c4819089dcc3689f322529 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.