Triple
T8494804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPCE |
E201070
|
entity |
| Predicate | delistingAnnounced |
P83038
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [SPCE, delistingAnnounced, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delistingAnnounced Context triple: [SPCE, delistingAnnounced, 2024]
-
A.
delisted
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
B.
discontinuationAnnouncedBy
Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
-
C.
reasonForDelisting
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
-
D.
withdrawalAnnouncedBy
Indicates that an entity’s withdrawal (e.g., from an agreement, position, or situation) has been publicly announced or declared by a specified agent or source.
-
E.
discontinuationAnnouncementDate
Indicates the date on which an official announcement is made that something (such as a product, service, or feature) will be discontinued.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.