Triple
T30842826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica M-mount |
E785557
|
entity |
| Predicate | supportsFocusingMethod |
P142681
|
FINISHED |
| Object | rangefinder coupling |
—
|
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: rangefinder coupling | Statement: [Leica M-mount, supportsFocusingMethod, rangefinder coupling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFocusingMethod Context triple: [Leica M-mount, supportsFocusingMethod, rangefinder coupling]
-
A.
hasFocusMethod
chosen
Indicates that an entity employs a particular method or approach to direct or manage focus or attention.
-
B.
requiresFocus
Indicates that performing or engaging with something demands concentrated attention or mental effort.
-
C.
mayProvideFocus
Indicates that one entity can potentially direct attention, emphasis, or concentration toward another entity or aspect.
-
D.
isInternalFocusing
Indicates a relationship where attention, processing, or activity is directed inward within a system, entity, or structure rather than toward external elements.
-
E.
hasFocusBehavior
Indicates that an entity exhibits a particular behavior or set of actions when it gains or has input focus.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 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, 8:45 p.m.