Triple
T30428163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 16-35mm f/2.8 GM |
E774089
|
entity |
| Predicate | opticalDesignGroups |
P171295
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Sony FE 16-35mm f/2.8 GM, opticalDesignGroups, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalDesignGroups Context triple: [Sony FE 16-35mm f/2.8 GM, opticalDesignGroups, 13]
-
A.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
B.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
C.
lensConstructionElements
Indicates that a lens is composed of, or incorporates, specific optical elements in its construction.
-
D.
hasOpticalElement
Indicates that one entity includes, contains, or is equipped with a specific optical element as a component or part.
-
E.
opticalTechnology
Indicates that one entity employs or involves optical methods, devices, or systems as its primary technology.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 8:06 p.m.