Triple
T11320375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanesboro, Minnesota |
E268075
|
entity |
| Predicate | tourismWebsite |
P27567
|
FINISHED |
| Object | https://www.lanesboro.com/ |
—
|
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: https://www.lanesboro.com/ | Statement: [Lanesboro, Minnesota, tourismWebsite, https://www.lanesboro.com/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismWebsite Context triple: [Lanesboro, Minnesota, tourismWebsite, https://www.lanesboro.com/]
-
A.
hasTourismWebsite
chosen
Indicates that an entity has an associated official website specifically dedicated to providing tourism-related information about it.
-
B.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
C.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
D.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
E.
tourDocumented
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9de875481908acfa56015d4b46f |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.