Triple
T30811230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7R III |
E784649
|
entity |
| Predicate | hasSilentShootingMode |
P169652
|
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, hasSilentShootingMode, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSilentShootingMode Context triple: [Sony α7R III, hasSilentShootingMode, Yes]
-
A.
silentShooting
chosen
Indicates performing a shooting action in a way that produces little or no detectable noise.
-
B.
hasShutterSpeedDial
Indicates that an object possesses a dedicated control or mechanism for adjusting shutter speed.
-
C.
hasElectronicShutter
Indicates that an entity is equipped with or supports an electronic shutter mechanism for capturing images without a mechanical shutter.
-
D.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
-
E.
hasShootingPosition
Indicates that an entity has a designated location or spot from which shooting (e.g., firing a weapon or taking a shot) is performed.
- 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:43 p.m.