Triple
T5550166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyresö Palace |
E145505
|
entity |
| Predicate | hasTouristAmenity |
P55845
|
FINISHED |
| Object | guided tours |
—
|
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: guided tours | Statement: [Tyresö Palace, hasTouristAmenity, guided tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristAmenity Context triple: [Tyresö Palace, hasTouristAmenity, guided tours]
-
A.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
B.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
C.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
-
D.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
E.
hasTourismResource
chosen
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe2aef481909944bc582c1f67a4 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.