Triple
T31008906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-E1 |
E790151
|
entity |
| Predicate | hasExposureCompensationDial |
P180972
|
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, hasExposureCompensationDial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExposureCompensationDial Context triple: [Fujifilm X-E1, hasExposureCompensationDial, true]
-
A.
exposureCompensation
Indicates an adjustment applied to increase or decrease the overall brightness of an exposure relative to the camera’s metered value.
-
B.
exposureCompensationRange
Indicates the range of exposure compensation values that can be applied to adjust image brightness relative to the camera’s metered exposure.
-
C.
hasShutterSpeedDial
Indicates that an object possesses a dedicated control or mechanism for adjusting shutter speed.
-
D.
exposureModes
Indicates the different ways or conditions under which an entity can be exposed to another entity, factor, or influence.
-
E.
hasElectronicShutter
Indicates that an entity is equipped with or supports an electronic shutter mechanism for capturing images without a mechanical shutter.
- 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_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 29, 2026, 8:57 p.m.