Triple
T30358095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EF lens mount |
E772200
|
entity |
| Predicate | mechanicalApertureCoupling |
P11991
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Canon EF lens mount, mechanicalApertureCoupling, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalApertureCoupling Context triple: [Canon EF lens mount, mechanicalApertureCoupling, no]
-
A.
hasApertureShape
Indicates that an entity’s aperture (opening) has a specific geometric or descriptive shape.
-
B.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
C.
requiresTelescopeAperture
Indicates that performing the specified observation or task depends on using a telescope with at least a certain aperture size.
-
D.
connectorDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a connector used to link or interface components.
-
E.
mechanicalKeying
chosen
Indicates that one entity physically engages or interlocks with another through a shaped mechanical interface (such as keys, slots, or profiles) to ensure correct positioning, alignment, or coupling.
- 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_69f682417ec08190982dd9acf7219742 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:57 p.m.