Triple
T27237917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dax |
E687116
|
entity |
| Predicate | primaryTouristAttractionType |
P8077
|
FINISHED |
| Object | thermal spa facilities |
—
|
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: thermal spa facilities | Statement: [Dax, primaryTouristAttractionType, thermal spa facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTouristAttractionType Context triple: [Dax, primaryTouristAttractionType, thermal spa facilities]
-
A.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
B.
primaryTourismHub
Indicates that a location serves as the main center or focal point for tourism activities within a given area or region.
-
C.
attractionType
chosen
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
D.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
E.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: April 27, 2026, 10:34 a.m.