Triple
T30644148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS M6 Mark II |
E780072
|
entity |
| Predicate | eyeDetectionAF |
P88980
|
FINISHED |
| Object | supported |
—
|
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: supported | Statement: [Canon EOS M6 Mark II, eyeDetectionAF, supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeDetectionAF Context triple: [Canon EOS M6 Mark II, eyeDetectionAF, supported]
-
A.
supportsRealTimeEyeAF
chosen
Indicates that the subject provides real-time autofocus functionality specifically for tracking and focusing on a subject’s eyes.
-
B.
eyeFeatureObserved
Indicates that a specific characteristic or condition of the eye has been detected or recorded through observation.
-
C.
faceVisibility
Indicates that one entity’s face is visible to another entity or from a particular viewpoint.
-
D.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
E.
eyeLocation
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a58cd808190bc1cdaa106291084 |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.