Triple
T30358201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon FTZ mount adapter |
E772202
|
entity |
| Predicate | supportsApertureControl |
P84809
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nikon FTZ mount adapter, supportsApertureControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsApertureControl Context triple: [Nikon FTZ mount adapter, supportsApertureControl, true]
-
A.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
B.
hasApertureStop
Indicates that one entity includes or is equipped with an aperture stop that limits or controls the light passing through an optical system.
-
C.
supportsCameraControl
chosen
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
D.
hasApertureRing
Indicates that one object possesses a physical aperture control ring as a feature or component.
-
E.
hasShutterSpeedDial
Indicates that an object possesses a dedicated control or mechanism for adjusting shutter speed.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:57 p.m.