Triple
T452427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skype |
E7156
|
entity |
| Predicate | acquisitionDateByMicrosoft |
P2754
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Skype, acquisitionDateByMicrosoft, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionDateByMicrosoft Context triple: [Skype, acquisitionDateByMicrosoft, 2011]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
C.
recognizedAsOfficeSince
Indicates that an entity has been officially designated or acknowledged as an office starting from a specific point in time.
-
D.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
E.
knownSince
Indicates the point in time from which one entity has been aware of, acquainted with, or in possession of knowledge about another 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef854f7481909dc2207faf0327ec |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.