Triple
T31008905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-E1 |
E790151
|
entity |
| Predicate | hasShutterSpeedDial |
P179513
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fujifilm X-E1, hasShutterSpeedDial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShutterSpeedDial Context triple: [Fujifilm X-E1, hasShutterSpeedDial, true]
-
A.
shutterSpeed
Indicates the exposure time setting of a camera, defining how long the shutter remains open during an image capture.
-
B.
hasElectronicShutter
Indicates that an entity is equipped with or supports an electronic shutter mechanism for capturing images without a mechanical shutter.
-
C.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
-
D.
flashSyncSpeedMechanical
Indicates the maximum shutter speed at which a mechanical shutter can synchronize properly with a flash.
-
E.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 29, 2026, 8:57 p.m.