Triple
T5637409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Fyre |
E124179
|
entity |
| Predicate | parkOpeningYearRelation |
P42285
|
FINISHED |
| Object | opened in park's inaugural season |
—
|
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: opened in park's inaugural season | Statement: [Dragon Fyre, parkOpeningYearRelation, opened in park's inaugural season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkOpeningYearRelation Context triple: [Dragon Fyre, parkOpeningYearRelation, opened in park's inaugural season]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
originalParkOpeningRelation
chosen
Indicates the relationship between a park and the event or date of its initial public opening.
-
C.
venueSinceYear
Indicates that a venue has been operating or established since a specified year.
-
D.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
E.
openingDateAsPark
Indicates the date on which a place or area was first officially opened and began operating as a park.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022820b7c81908f79c0a124d6b940 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.