Triple
T19318120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pier 1 Imports |
E483150
|
entity |
| Predicate | announcedLiquidationOfAllStores |
P43843
|
FINISHED |
| Object | May 2020 |
—
|
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: May 2020 | Statement: [Pier 1 Imports, announcedLiquidationOfAllStores, May 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedLiquidationOfAllStores Context triple: [Pier 1 Imports, announcedLiquidationOfAllStores, May 2020]
-
A.
announcedPermanentClosure
chosen
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
-
B.
liquidationBegan
Indicates that the process of winding up and dissolving an entity, typically by selling its assets to pay creditors, has started.
-
C.
closedAsStore
Indicates that an entity has ceased operations specifically in its role or function as a store.
-
D.
purposeOfLiquidation
Indicates that a liquidation event is carried out for a specific intended purpose or objective.
-
E.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d85046c81909d972a6b369b0c2b |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.