Triple
T14533317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Slidewinder |
E340968
|
entity |
| Predicate | parkThemeAlignment |
P114808
|
FINISHED |
| Object | Smoky Mountain heritage |
—
|
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 Mountain heritage | Statement: [Mountain Slidewinder, parkThemeAlignment, Smoky Mountain heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkThemeAlignment Context triple: [Mountain Slidewinder, parkThemeAlignment, Smoky Mountain heritage]
-
A.
parkSectionTheme
Indicates that a particular section of a park is associated with a specific thematic concept or style.
-
B.
themeParkAttractionAt
Indicates that a specific theme park attraction is located at or associated with a particular theme park or site.
-
C.
themeParkAttraction
Indicates that something is an attraction or ride located within a theme park.
-
D.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
-
E.
themeParkComplex
Indicates a relationship where one entity is a theme park complex that encompasses or is composed of the other entity or entities.
- 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_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. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:22 a.m.