Triple
T37659056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distagon lens design |
E937671
|
entity |
| Predicate | hasAngleOfViewCategory |
P194691
|
FINISHED |
| Object | wide‑angle |
—
|
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: wide‑angle | Statement: [Distagon lens design, hasAngleOfViewCategory, wide‑angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAngleOfViewCategory Context triple: [Distagon lens design, hasAngleOfViewCategory, wide‑angle]
-
A.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
B.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
C.
angleOfViewFullFrame
Indicates the angle of view produced by a lens when used on a full-frame (35mm) sensor or format.
-
D.
angleOfViewAPSC
Indicates the angle of view produced by a lens when used on an APS-C (crop-sensor) camera format.
-
E.
angleOfViewMax
Indicates the maximum angle or field of view within which something can be seen, captured, or effectively observed.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: May 3, 2026, 4:18 p.m.