Triple
T30382409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EF-S lens mount |
E772865
|
entity |
| Predicate | designedForCropFactor |
P169098
|
FINISHED |
| Object | 1.6x |
—
|
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: 1.6x | Statement: [Canon EF-S lens mount, designedForCropFactor, 1.6x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForCropFactor Context triple: [Canon EF-S lens mount, designedForCropFactor, 1.6x]
-
A.
cropFactor
chosen
Indicates the ratio between a camera sensor’s dimensions and a reference format (typically 35mm/full-frame), expressing how much the field of view is effectively “cropped” compared to that standard.
-
B.
equivalentFocalLengthOnAPSC
Indicates the focal length on an APS-C sensor that would provide the same field of view as a given focal length on a full-frame (35mm) sensor.
-
C.
viewfinderResolution
Indicates the resolution or level of detail provided by a device’s viewfinder display.
-
D.
hasLongFocalLength
Indicates that one entity possesses or is characterized by a focal length that is relatively long compared to a standard or reference.
-
E.
hasWideCamera
Indicates that an entity is equipped with or features a wide-angle camera.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 29, 2026, 8:01 p.m.