Triple
T30811231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7R III |
E784649
|
entity |
| Predicate | supportsPixelShiftMultiShooting |
P57608
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Sony α7R III, supportsPixelShiftMultiShooting, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPixelShiftMultiShooting Context triple: [Sony α7R III, supportsPixelShiftMultiShooting, Yes]
-
A.
hasWideCamera
Indicates that an entity is equipped with or features a wide-angle camera.
-
B.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
C.
hasPhotoFeature
chosen
Indicates that an entity possesses a characteristic, capability, or option specifically related to photos or photography.
-
D.
hasOpticalImageStabilization
Indicates that a device or component includes a feature that reduces image blur caused by camera movement during capture.
-
E.
hasUltraWideCamera
Indicates that an entity is equipped with or includes an ultra-wide camera as one of its features.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:43 p.m.