Triple
T30532243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R6 |
E777036
|
entity |
| Predicate | phaseDetectAFPoints |
P88979
|
FINISHED |
| Object | up to 6072 selectable AF positions |
—
|
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 6072 selectable AF positions | Statement: [Canon EOS R6, phaseDetectAFPoints, up to 6072 selectable AF positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseDetectAFPoints Context triple: [Canon EOS R6, phaseDetectAFPoints, up to 6072 selectable AF positions]
-
A.
autofocusPoints
chosen
Indicates the relationship between a camera (or imaging device) and the specific focus points it can automatically select or use for focusing.
-
B.
timingOfPoints
Indicates the temporal relationship or sequence in which the points or events occur.
-
C.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
D.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
E.
tryPoints
Indicates an attempt by one entity to score or gain points, typically through some action or effort directed toward achieving those points.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6884ceb18819082e8c4002d1faa95 |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:18 p.m.