Triple
T9213018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrevieja |
E221170
|
entity |
| Predicate | hasTouristProfile |
P86886
|
FINISHED |
| Object | sun and beach destination |
—
|
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: sun and beach destination | Statement: [Torrevieja, hasTouristProfile, sun and beach destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristProfile Context triple: [Torrevieja, hasTouristProfile, sun and beach destination]
-
A.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
B.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
C.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
D.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
hasTouristRank
Indicates that an entity is assigned a specific rank or rating based on its attractiveness or importance as a tourist destination.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda05406081909893bec3a092d3ce |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:27 p.m.