Triple
T36621422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serial Thriller |
E904048
|
entity |
| Predicate | openingYearAtGeaugaLake |
P84798
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Serial Thriller, openingYearAtGeaugaLake, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingYearAtGeaugaLake Context triple: [Serial Thriller, openingYearAtGeaugaLake, 1998]
-
A.
yearOpenedToPublic
chosen
Indicates the calendar year in which something (such as a place, facility, or service) was first made accessible to the general public.
-
B.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
openingDateAsPark
Indicates the date on which a place or area was first officially opened and began operating as a park.
-
D.
openingYearAsExpoSite
Indicates the year in which a location first opened or began operating as an exposition (expo) site.
-
E.
approximateOpeningYear
Indicates the estimated or roughly determined year in which something (such as a facility, venue, or organization) began operating or opened.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:11 p.m.