Triple
T15934667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisneyQuest |
E386409
|
entity |
| Predicate | ChicagoLocationClosingDate |
P121050
|
FINISHED |
| Object | 2001-09-04 |
—
|
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: 2001-09-04 | Statement: [DisneyQuest, ChicagoLocationClosingDate, 2001-09-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChicagoLocationClosingDate Context triple: [DisneyQuest, ChicagoLocationClosingDate, 2001-09-04]
-
A.
restaurantClosureDate
Indicates the date on which a restaurant ceases or ceased operations, marking its official closure.
-
B.
closedCityDuring
Indicates that a city is not accessible or operational during a specified time period or interval.
-
C.
chicagoTerminus
Indicates that a route, line, or service has its final terminus or endpoint in Chicago.
-
D.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
E.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
- F. None of above. chosen
Provenance (4 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:53 a.m.