Triple
T8654573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oban |
E205381
|
entity |
| Predicate | tourismCharacteristic |
P84159
|
FINISHED |
| Object | high seasonal visitor numbers |
—
|
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: high seasonal visitor numbers | Statement: [Oban, tourismCharacteristic, high seasonal visitor numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismCharacteristic Context triple: [Oban, tourismCharacteristic, high seasonal visitor numbers]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
D.
tourismDraw
Indicates that one entity attracts tourists or visitor interest to another entity or location.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48432568819093b9a867b4f62b78 |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc473e44988190a3b02498e5fff668 |
completed | March 31, 2026, 10:14 p.m. |
Created at: March 30, 2026, 6:29 p.m.