Triple
T30842860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica M-mount |
E785557
|
entity |
| Predicate | hasMechanicalCoupling |
P22536
|
FINISHED |
| Object | rangefinder cam |
—
|
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 cam | Statement: [Leica M-mount, hasMechanicalCoupling, rangefinder cam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMechanicalCoupling Context triple: [Leica M-mount, hasMechanicalCoupling, rangefinder cam]
-
A.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
B.
hasCoupling
chosen
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
C.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
D.
wingCouplingMechanism
Indicates the type or presence of a structural or functional mechanism by which wings are linked or coupled to each other or to another body part during use.
-
E.
hasPegMechanism
Indicates that one entity includes or uses a peg-based mechanism in relation to another entity.
- 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_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 8:45 p.m.