Triple
T17121948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Younkers |
E415488
|
entity |
| Predicate | storeClosuresCompleted |
P56128
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Younkers, storeClosuresCompleted, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storeClosuresCompleted Context triple: [Younkers, storeClosuresCompleted, 2018]
-
A.
closureCompleted
chosen
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
B.
closedAsStore
Indicates that an entity has ceased operations specifically in its role or function as a store.
-
C.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
D.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
E.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80ac2cc819084fab829917c950a |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.