Triple
T30698693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 100-400mm f/4.5-5.6 GM OSS |
E781549
|
entity |
| Predicate | minimumFocalLength |
P169099
|
FINISHED |
| Object | 100mm |
—
|
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: 100mm | Statement: [Sony FE 100-400mm f/4.5-5.6 GM OSS, minimumFocalLength, 100mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumFocalLength Context triple: [Sony FE 100-400mm f/4.5-5.6 GM OSS, minimumFocalLength, 100mm]
-
A.
angleOfViewMin
Indicates the minimum angle of view that a sensor, camera, or observer can cover or perceive.
-
B.
minimumAperture
Indicates the smallest opening or aperture size that a system, device, or component can achieve or operate with.
-
C.
minimumFocusDistance
Indicates the shortest distance at which a system (such as a camera or sensor) can focus on a subject while maintaining acceptable image sharpness.
-
D.
minimumWorkingDistance
Indicates the shortest allowable distance that must be maintained between two entities for them to operate or interact safely or effectively.
-
E.
focalLengthRange
chosen
Indicates the range of focal lengths over which an optical device (such as a lens) can operate or be adjusted.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:34 p.m.