Triple
T1611921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skype for Business Online |
E34631
|
entity |
| Predicate | announcement |
P4650
|
FINISHED |
| Object | retirement in favor of Microsoft Teams |
—
|
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: retirement in favor of Microsoft Teams | Statement: [Skype for Business Online, announcement, retirement in favor of Microsoft Teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcement Context triple: [Skype for Business Online, announcement, retirement in favor of Microsoft Teams]
-
A.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
B.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
-
C.
announcedThat
chosen
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
announcementLocation
Indicates the place or venue where an announcement is made or presented.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.