Triple
T30358533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 200-600mm f/5.6-6.3 G OSS |
E772209
|
entity |
| Predicate | opticalConstructionGroups |
P169490
|
FINISHED |
| Object | 17 groups |
—
|
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: 17 groups | Statement: [Sony FE 200-600mm f/5.6-6.3 G OSS, opticalConstructionGroups, 17 groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalConstructionGroups Context triple: [Sony FE 200-600mm f/5.6-6.3 G OSS, opticalConstructionGroups, 17 groups]
-
A.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
B.
lensConstructionElements
chosen
Indicates that a lens is composed of, or incorporates, specific optical elements in its construction.
-
C.
opticalTechnology
Indicates that one entity employs or involves optical methods, devices, or systems as its primary technology.
-
D.
hasOpticalElement
Indicates that one entity includes, contains, or is equipped with a specific optical element as a component or part.
-
E.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:57 p.m.