Triple
T30358198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon FTZ mount adapter |
E772202
|
entity |
| Predicate | supportsMeteringWith |
P169096
|
FINISHED |
| Object | Nikon F-mount lenses |
E772203
|
NE 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: Nikon F-mount lenses | Statement: [Nikon FTZ mount adapter, supportsMeteringWith, Nikon F-mount lenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMeteringWith Context triple: [Nikon FTZ mount adapter, supportsMeteringWith, Nikon F-mount lenses]
-
A.
meteringSupport
chosen
Indicates that one entity provides or is compatible with metering capabilities (such as measurement, tracking, or billing of usage) for another entity.
-
B.
hasMeter
Indicates that one entity possesses, uses, or is associated with a specific meter (a measuring device or metrical pattern).
-
C.
supportsInstrument
Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
-
D.
meteringSystem
Indicates that one entity functions as a metering system used to measure, record, or regulate quantities or usage related to another entity.
-
E.
supportsMonetizationProgram
Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
- F. None of above.
Provenance (4 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27893994548190958b3949339a6bd6 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:57 p.m.