Triple
T24262610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Dollar City |
E604747
|
entity |
| Predicate | hasLiveEntertainmentType |
P51190
|
FINISHED |
| Object | stage shows |
—
|
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: stage shows | Statement: [Silver Dollar City, hasLiveEntertainmentType, stage shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveEntertainmentType Context triple: [Silver Dollar City, hasLiveEntertainmentType, stage shows]
-
A.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
B.
hasEntertainmentVenue
Indicates that an entity possesses, contains, or is associated with an entertainment venue as part of its facilities or offerings.
-
C.
hasEntertainmentOptions
chosen
Indicates that an entity provides or includes one or more forms of entertainment or leisure activities as options.
-
D.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
E.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c691eb08190b6fbda8f187d7427 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.