Triple
T30698695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 100-400mm f/4.5-5.6 GM OSS |
E781549
|
entity |
| Predicate | maximumApertureWide |
P181154
|
FINISHED |
| Object | f/4.5 |
—
|
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: f/4.5 | Statement: [Sony FE 100-400mm f/4.5-5.6 GM OSS, maximumApertureWide, f/4.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumApertureWide Context triple: [Sony FE 100-400mm f/4.5-5.6 GM OSS, maximumApertureWide, f/4.5]
-
A.
maximumApertureAtWideEnd
chosen
Indicates the largest lens aperture value available when the zoom lens is set to its widest focal length.
-
B.
maximumAperture
Indicates the widest opening size that an optical system (such as a lens) can achieve to allow light to pass through.
-
C.
maximumFocalLength
Indicates the greatest focal length value that an optical device or system can achieve.
-
D.
maximumApertureAtTeleEnd
Indicates the largest lens aperture value achievable when the zoom lens is set to its longest (telephoto) focal length.
-
E.
angleOfViewMax
Indicates the maximum angle or field of view within which something can be seen, captured, or effectively observed.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:34 p.m.