Triple
T22298652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ness of Brodgar |
E551192
|
entity |
| Predicate | hasVisitorTours |
P7952
|
FINISHED |
| Object | guided excavation tours in summer |
—
|
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 excavation tours in summer | Statement: [Ness of Brodgar, hasVisitorTours, guided excavation tours in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorTours Context triple: [Ness of Brodgar, hasVisitorTours, guided excavation tours in summer]
-
A.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
B.
hasTour
chosen
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
D.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
hasIslandTourism
Indicates that an entity engages in or supports tourism activities specifically related to islands.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15722c3348190b63eb49764ef132d |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.