Triple
T31256723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-T20 |
E796993
|
entity |
| Predicate | driveModeDial |
P85075
|
FINISHED |
| Object | top-plate drive mode selector |
—
|
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: top-plate drive mode selector | Statement: [Fujifilm X-T20, driveModeDial, top-plate drive mode selector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveModeDial Context triple: [Fujifilm X-T20, driveModeDial, top-plate drive mode selector]
-
A.
driveModes
chosen
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
B.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
C.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
driveScheme
Indicates that one entity operates or controls a scheme, system, or initiative, causing it to function or move forward.
-
E.
instrumentMode
Indicates the manner, setting, or operational mode in which an instrument is used to perform an action or measurement.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 9:12 p.m.