Triple
T3805250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-Trade |
E92989
|
entity |
| Predicate | delisted |
P51857
|
FINISHED |
| Object | 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: 2020 | Statement: [E-Trade, delisted, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delisted Context triple: [E-Trade, delisted, 2020]
-
A.
divested
Indicates that one entity has sold off, relinquished, or otherwise disposed of ownership, control, or interest in another entity or asset.
-
B.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
C.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
D.
withdrawn
Indicates that an entity has removed or taken back a previously offered, submitted, or available item, action, or commitment.
-
E.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:16 p.m.