Triple
T15158779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Pixel 6 Pro |
E362150
|
entity |
| Predicate | aiFeatures |
P116964
|
FINISHED |
| Object | on-device AI processing |
—
|
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: on-device AI processing | Statement: [Google Pixel 6 Pro, aiFeatures, on-device AI processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aiFeatures Context triple: [Google Pixel 6 Pro, aiFeatures, on-device AI processing]
-
A.
visualFeature
Indicates a relationship where one entity possesses or exhibits a particular visual characteristic or attribute of another entity.
-
B.
intelligenceService
Indicates that one entity functions as an intelligence or security service organization for another entity.
-
C.
featuresMood
Indicates that something includes, presents, or conveys a particular mood or emotional atmosphere.
-
D.
identityFeatures
Indicates that certain characteristics or attributes are used to define, distinguish, or uniquely identify an entity.
-
E.
featuresSample
Indicates that an entity includes or presents a particular sample as one of its components or examples.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060dd71881908ecc4a4f52d438a5 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:08 a.m.