Triple
T31256701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-T20 |
E796993
|
entity |
| Predicate | phaseDetectAF |
P110321
|
FINISHED |
| Object | on-sensor phase detection |
—
|
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: on-sensor phase detection | Statement: [Fujifilm X-T20, phaseDetectAF, on-sensor phase detection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseDetectAF Context triple: [Fujifilm X-T20, phaseDetectAF, on-sensor phase detection]
-
A.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
B.
phaseUsed
chosen
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
-
C.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
D.
phaseDifferenceDependsOn
Indicates that the phase difference between two signals or waves is determined by, or varies as a function of, another specified quantity or condition.
-
E.
phaseIncrement
Indicates the amount by which a phase value is advanced or updated during each step or cycle in a process or signal.
- 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_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:12 p.m.