Triple
T5480397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VoWiFi |
E123452
|
entity |
| Predicate | introducedInIndustry |
P8259
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [VoWiFi, introducedInIndustry, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInIndustry Context triple: [VoWiFi, introducedInIndustry, 2010s]
-
A.
emergedInIndustry
Indicates that an entity first appeared, originated, or came into prominence within a specified industry.
-
B.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
C.
introducedInMarket
Indicates that an entity was first made available or launched for sale within a particular market or marketplace.
-
D.
usedInIndustry
Indicates that something is employed or applied within a particular industry or industrial sector.
-
E.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.