Triple
T31149489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-E4 |
E794031
|
entity |
| Predicate | maxShutterSpeedMechanical |
P88984
|
FINISHED |
| Object | 1/4000 s |
—
|
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: 1/4000 s | Statement: [Fujifilm X-E4, maxShutterSpeedMechanical, 1/4000 s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxShutterSpeedMechanical Context triple: [Fujifilm X-E4, maxShutterSpeedMechanical, 1/4000 s]
-
A.
maximumShutterSpeed
chosen
Indicates the highest shutter speed value that can be set or achieved in a given photographic or imaging context.
-
B.
shutterSpeed
Indicates the exposure time setting of a camera, defining how long the shutter remains open during an image capture.
-
C.
flashSyncSpeedMechanical
Indicates the maximum shutter speed at which a mechanical shutter can synchronize properly with a flash.
-
D.
flashSyncSpeedElectronic
Indicates the maximum shutter speed at which an electronic shutter can synchronize properly with a flash.
-
E.
angleOfViewMax
Indicates the maximum angle or field of view within which something can be seen, captured, or effectively observed.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.