Triple
T30842945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica screw-mount lenses (via adapter on M bodies) |
E785559
|
entity |
| Predicate | isMechanicalInterface |
P134343
|
FINISHED |
| Object | purely mechanical |
—
|
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: purely mechanical | Statement: [Leica screw-mount lenses (via adapter on M bodies), isMechanicalInterface, purely mechanical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMechanicalInterface Context triple: [Leica screw-mount lenses (via adapter on M bodies), isMechanicalInterface, purely mechanical]
-
A.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
B.
hasMechanicalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
D.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
-
E.
hasCommunicationInterface
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
- 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_69f691443b108190acb7823c16ace379 |
completed | May 3, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:45 p.m.