Triple
T19460596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paragon Park |
E486856
|
entity |
| Predicate | GiantCoasterOpeningYear |
P84798
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Paragon Park, GiantCoasterOpeningYear, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GiantCoasterOpeningYear Context triple: [Paragon Park, GiantCoasterOpeningYear, 1917]
-
A.
spaceMountainOpeningYear
Indicates the calendar year in which a specific Space Mountain attraction first opened to the public.
-
B.
originalAttractionOpeningDate
Indicates the date on which the attraction first opened to the public in its original form or location.
-
C.
isFamilyCoaster
Indicates that a roller coaster is designed to be suitable and enjoyable for riders of all ages, including children and families.
-
D.
rollerCoasterType
Indicates that one entity is classified as a specific type or category of roller coaster in relation to another entity.
-
E.
yearOpenedToPublic
chosen
Indicates the calendar year in which something (such as a place, facility, or service) was first made accessible to the general public.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.