Triple
T13894434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlackBerry Messenger |
E334051
|
entity |
| Predicate | serviceShutdown |
P84963
|
FINISHED |
| Object | consumer version shut down in May 2019 |
—
|
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: consumer version shut down in May 2019 | Statement: [BlackBerry Messenger, serviceShutdown, consumer version shut down in May 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceShutdown Context triple: [BlackBerry Messenger, serviceShutdown, consumer version shut down in May 2019]
-
A.
shutdownCapability
Indicates the ability or permission for one entity to power off, deactivate, or terminate the operation of another entity or system.
-
B.
serviceRetirement
Indicates that an entity ends or withdraws a service, marking it as no longer available or in active use.
-
C.
serviceEnded
chosen
Indicates that a previously active service or service relationship has come to an end.
-
D.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
E.
centerEngineShutdown
Indicates that the central engine in a multi-engine system has been turned off or has ceased operating.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.