Triple
T4036542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixel 7 Pro |
E83840
|
entity |
| Predicate | hasMainRearCameraResolution |
P17636
|
FINISHED |
| Object | 50 MP |
—
|
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: 50 MP | Statement: [Pixel 7 Pro, hasMainRearCameraResolution, 50 MP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRearCameraResolution Context triple: [Pixel 7 Pro, hasMainRearCameraResolution, 50 MP]
-
A.
rearCameraMainResolution
chosen
Indicates the primary resolution (in megapixels or similar units) of a device’s main rear-facing camera.
-
B.
hasOuterSelfieCamera
Indicates that an entity (typically a device) is equipped with a front-facing camera intended for taking selfies.
-
C.
hasInnerSelfieCamera
Indicates that an object (typically a device) is equipped with a front-facing or inward-facing selfie camera.
-
D.
rearCameraFeature
Indicates that an entity has a specific characteristic, capability, or attribute related to its rear-facing camera.
-
E.
rearCameraCount
Indicates the number of camera units located on the rear side of a device.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb349e648190b9f227df4cd76fa0 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.