Triple
T826963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tynwald Day |
E17874
|
entity |
| Predicate | tourismImpact |
P530
|
FINISHED |
| Object | attracts visitors to the Isle of Man |
—
|
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: attracts visitors to the Isle of Man | Statement: [Tynwald Day, tourismImpact, attracts visitors to the Isle of Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismImpact Context triple: [Tynwald Day, tourismImpact, attracts visitors to the Isle of Man]
-
A.
tourismImportance
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
B.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
tourismRegulation
Indicates that an authority establishes or enforces rules, policies, or controls governing tourism activities or the tourism sector.
-
D.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
E.
isTouristDestination
chosen
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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab989748819091a3809a747a1c5b |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.