Triple
T30949533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-S20 |
E788495
|
entity |
| Predicate | continuousShootingMechanicalShutter |
P170045
|
FINISHED |
| Object | up to 8 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: up to 8 fps | Statement: [Fujifilm X-S20, continuousShootingMechanicalShutter, up to 8 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousShootingMechanicalShutter Context triple: [Fujifilm X-S20, continuousShootingMechanicalShutter, up to 8 fps]
-
A.
maxContinuousShooting
chosen
Indicates the maximum number of photos a camera can continuously capture in rapid succession before it must pause or slow down.
-
B.
flashSyncSpeedMechanical
Indicates the maximum shutter speed at which a mechanical shutter can synchronize properly with a flash.
-
C.
hasElectronicShutter
Indicates that an entity is equipped with or supports an electronic shutter mechanism for capturing images without a mechanical shutter.
-
D.
hasShutterSpeedDial
Indicates that an object possesses a dedicated control or mechanism for adjusting shutter speed.
-
E.
shutterSpeed
Indicates the exposure time setting of a camera, defining how long the shutter remains open during an image capture.
- 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_69f224c180f88190ad177372ee02b7e2 |
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:53 p.m.