Triple
T30358210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon FTZ mount adapter |
E772202
|
entity |
| Predicate | retainsLensFunctions |
P77830
|
FINISHED |
| Object | autofocus |
—
|
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: autofocus | Statement: [Nikon FTZ mount adapter, retainsLensFunctions, autofocus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainsLensFunctions Context triple: [Nikon FTZ mount adapter, retainsLensFunctions, autofocus]
-
A.
retainsFunction
chosen
Indicates that an entity continues to perform or preserve its original function despite changes in context, condition, or form.
-
B.
usesAsLens
Indicates that one entity employs another entity as a lens or optical element through which to view, focus, or modify light or images.
-
C.
originalLens
Indicates that one lens is the initial or source lens from which another lens or lens configuration is derived or referenced.
-
D.
effectOnLens
Indicates the influence or impact that one entity has on the properties, behavior, or performance of a lens.
-
E.
usesLensBrand
Indicates that one entity employs or operates using a lens produced by a specific brand.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682417ec08190982dd9acf7219742 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:57 p.m.