Triple
T21568265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuance Communications |
E532215
|
entity |
| Predicate | delistedOn |
P118276
|
FINISHED |
| Object | 2022-03-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: 2022-03-04 | Statement: [Nuance Communications, delistedOn, 2022-03-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delistedOn Context triple: [Nuance Communications, delistedOn, 2022-03-04]
-
A.
delistedBy
Indicates that one entity has removed another entity from an official list, registry, or marketplace.
-
B.
delisted
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
C.
delistingAnnounced
Indicates that an official announcement has been made that an entity (such as a security, product, or listing) will be removed from a marketplace, exchange, or listing platform.
-
D.
delistingRelatedEventDate
chosen
Indicates the date on which an event related to a security’s delisting occurred.
-
E.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cad95c8190ab165ced6f242302 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.