Triple
T38641032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone SE (2nd generation) |
E938594
|
entity |
| Predicate | rearCameraVideoMaxResolution |
P187196
|
FINISHED |
| Object | 4K at 60 fps |
—
|
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: 4K at 60 fps | Statement: [iPhone SE (2nd generation), rearCameraVideoMaxResolution, 4K at 60 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rearCameraVideoMaxResolution Context triple: [iPhone SE (2nd generation), rearCameraVideoMaxResolution, 4K at 60 fps]
-
A.
rearCameraVideoResolution
chosen
Indicates the video resolution capability or setting of a device’s rear-facing camera.
-
B.
rearCameraMainResolution
Indicates the primary resolution (in megapixels or similar units) of a device’s main rear-facing camera.
-
C.
frontCameraVideoResolution
Indicates the video resolution capability or setting of a device’s front-facing camera.
-
D.
macroRearCameraResolution
Indicates the resolution capability of a device’s rear macro camera when capturing images.
-
E.
frontCameraResolution
Indicates the resolution quality or pixel count of a device’s front-facing (selfie) camera.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.