Triple
T1499858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qualcomm |
E29770
|
entity |
| Predicate | hasPatentPortfolioIn |
P28530
|
FINISHED |
| Object | 3G wireless technologies |
—
|
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: 3G wireless technologies | Statement: [Qualcomm, hasPatentPortfolioIn, 3G wireless technologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatentPortfolioIn Context triple: [Qualcomm, hasPatentPortfolioIn, 3G wireless technologies]
-
A.
numberOfPatents
Indicates the count of patents associated with a given entity.
-
B.
typeOfPatentsGranted
Indicates the specific categories or kinds of patents that have been officially granted to an entity.
-
C.
patentIn
Indicates that one entity holds or is associated with a patent located, filed, or registered in a particular jurisdiction, organization, or context represented by the other entity.
-
D.
patentHolder
Indicates that one entity legally owns the rights granted by a specific patent associated with another entity or invention.
-
E.
patent
Indicates that a legal protection has been granted to an entity for an invention, giving it exclusive rights to make, use, or sell that invention.
- F. None of above. chosen
Provenance (4 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f2d7f881909188a3e5614335cd |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:12 p.m.