Triple
T14746984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SkyCoaster |
E346497
|
entity |
| Predicate | hasThemeParkCategory |
P8648
|
FINISHED |
| Object | upcharge attraction |
—
|
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: upcharge attraction | Statement: [SkyCoaster, hasThemeParkCategory, upcharge attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeParkCategory Context triple: [SkyCoaster, hasThemeParkCategory, upcharge attraction]
-
A.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
-
B.
hasAttractionTheme
Indicates that something (such as a place, event, or attraction) is characterized by or associated with a particular theme or motif.
-
C.
themeParkAttractionAt
Indicates that a specific theme park attraction is located at or associated with a particular theme park or site.
-
D.
themeParkAccess
Indicates that an entity has permission or eligibility to enter or use the facilities and attractions of a theme park.
-
E.
hasAttractionType
chosen
Indicates that one entity is associated with a specific kind or category of attraction (e.g., tourist, cultural, natural).
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d116e88190828b163b18d80f68 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.