Triple
T347546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia dos Pescadores |
E6972
|
entity |
| Predicate | regionTourismCategory |
P3030
|
FINISHED |
| Object | Algarve beaches |
—
|
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: Algarve beaches | Statement: [Praia dos Pescadores, regionTourismCategory, Algarve beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTourismCategory Context triple: [Praia dos Pescadores, regionTourismCategory, Algarve beaches]
-
A.
tourismRegion
chosen
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
B.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
D.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
E.
tourismRegulation
Indicates that an authority establishes or enforces rules, policies, or controls governing tourism activities or the tourism sector.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.