Triple
T13644198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Movie Ride |
E326059
|
entity |
| Predicate | announcedClosureDate |
P102280
|
FINISHED |
| Object | 2017-07-15 |
—
|
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: 2017-07-15 | Statement: [The Great Movie Ride, announcedClosureDate, 2017-07-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedClosureDate Context triple: [The Great Movie Ride, announcedClosureDate, 2017-07-15]
-
A.
permanentClosureAnnouncementDate
chosen
Indicates the date on which an official announcement was made that something (such as a facility, service, or location) will be permanently closed.
-
B.
announcedClosure
Indicates that an entity has publicly declared the intention to shut down, discontinue, or close another entity or operation.
-
C.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
-
D.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
E.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5ac2af88190976abe6606994eef |
completed | April 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.