Triple
T11907068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primeval Whirl |
E283297
|
entity |
| Predicate | permanentClosureAnnouncementDate |
P102280
|
FINISHED |
| Object | 2020-07-16 |
—
|
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: 2020-07-16 | Statement: [Primeval Whirl, permanentClosureAnnouncementDate, 2020-07-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentClosureAnnouncementDate Context triple: [Primeval Whirl, permanentClosureAnnouncementDate, 2020-07-16]
-
A.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
B.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
C.
announcedPermanentClosure
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
D.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
-
E.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5264b2081909bda6c24abb89725 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.