Triple
T30358520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 200-600mm f/5.6-6.3 G OSS |
E772209
|
entity |
| Predicate | minimumAperture |
P172176
|
FINISHED |
| Object | f/32-36 |
—
|
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/32-36 | Statement: [Sony FE 200-600mm f/5.6-6.3 G OSS, minimumAperture, f/32-36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumAperture Context triple: [Sony FE 200-600mm f/5.6-6.3 G OSS, minimumAperture, f/32-36]
-
A.
angleOfViewMin
Indicates the minimum angle of view that a sensor, camera, or observer can cover or perceive.
-
B.
minimumWorkingDistance
Indicates the shortest allowable distance that must be maintained between two entities for them to operate or interact safely or effectively.
-
C.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
D.
rearCameraAperture
Indicates the size or f-stop value of the aperture used by a device’s rear-facing camera when capturing images or video.
-
E.
minimumSize
Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 7:57 p.m.