Triple
T30532300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 24mm f/1.4 GM |
E777037
|
entity |
| Predicate | hasApertureRing |
P185645
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sony FE 24mm f/1.4 GM, hasApertureRing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApertureRing Context triple: [Sony FE 24mm f/1.4 GM, hasApertureRing, yes]
-
A.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
B.
hasApertureShape
Indicates that an entity’s aperture (opening) has a specific geometric or descriptive shape.
-
C.
hasApertureClass
Indicates that one entity is classified according to a specific aperture category or class of another entity.
-
D.
apertureRingDeClickSwitch
Indicates that there is a control or mechanism to switch an aperture ring between clicked (detented) and smooth (de-clicked) operation.
-
E.
usesLensMount
Indicates that one device or component is designed to accept, attach to, or operate with a specific type of lens mount.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 29, 2026, 8:18 p.m.