Triple
T2472761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexa Internet |
E55013
|
entity |
| Predicate | serviceTermination |
P21869
|
FINISHED |
| Object | discontinued analytics services in 2022 |
—
|
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: discontinued analytics services in 2022 | Statement: [Alexa Internet, serviceTermination, discontinued analytics services in 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTermination Context triple: [Alexa Internet, serviceTermination, discontinued analytics services in 2022]
-
A.
recommendedTerminationOf
Indicates that one party has advised or proposed that another party’s role, contract, or activity should be ended.
-
B.
originalServiceEnded
chosen
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
C.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
D.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
E.
canTerminate
Indicates that one entity has the authority or ability to end or discontinue another entity, process, or relationship.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.