Triple
T16212707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Pool (Tamolitch Pool) |
E393505
|
entity |
| Predicate | visitorImpactConcern |
P118568
|
FINISHED |
| Object | trail erosion |
—
|
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: trail erosion | Statement: [Blue Pool (Tamolitch Pool), visitorImpactConcern, trail erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorImpactConcern Context triple: [Blue Pool (Tamolitch Pool), visitorImpactConcern, trail erosion]
-
A.
tourismImpactConcern
chosen
Indicates concern that tourism is having or may have negative impacts on a place, community, or environment.
-
B.
hasTourismImpactOn
Indicates that one entity affects or influences the tourism levels, patterns, or attractiveness of another entity.
-
C.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
D.
visitorInformation
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
E.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f2c1288190bfaed49c364bfa22 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.