Triple
T576690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qualcomm Snapdragon Wear |
E13772
|
entity |
| Predicate | computingPlatformType |
P9320
|
FINISHED |
| Object | low-power SoC |
—
|
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: low-power SoC | Statement: [Qualcomm Snapdragon Wear, computingPlatformType, low-power SoC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingPlatformType Context triple: [Qualcomm Snapdragon Wear, computingPlatformType, low-power SoC]
-
A.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
primaryOperatingEnvironment
chosen
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
-
C.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
D.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
E.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.