Triple
T14533657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoky Mountain Christmas |
E340980
|
entity |
| Predicate | regionAttractionFor |
P5644
|
FINISHED |
| Object | Smoky Mountains visitors |
—
|
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: Smoky Mountains visitors | Statement: [Smoky Mountain Christmas, regionAttractionFor, Smoky Mountains visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAttractionFor Context triple: [Smoky Mountain Christmas, regionAttractionFor, Smoky Mountains visitors]
-
A.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
B.
themeParkAttractionLocation
Indicates the specific place or area within a theme park where a particular attraction is situated.
-
C.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
D.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
E.
isMajorAttractionFor
chosen
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea053f9bc8190901b9d321811d881 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.