Triple
T30481924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony FE 85mm f/1.4 GM |
E775609
|
entity |
| Predicate | compatibleCameraType |
P182842
|
FINISHED |
| Object | Sony full-frame E-mount mirrorless camera |
—
|
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: Sony full-frame E-mount mirrorless camera | Statement: [Sony FE 85mm f/1.4 GM, compatibleCameraType, Sony full-frame E-mount mirrorless camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleCameraType Context triple: [Sony FE 85mm f/1.4 GM, compatibleCameraType, Sony full-frame E-mount mirrorless camera]
-
A.
usesCameraType
Indicates that one entity employs or operates a specific type or category of camera.
-
B.
hasCamera
Indicates that an entity is equipped with or possesses a camera.
-
C.
tipoDeCámara
Indicates the specific type or category of camera associated with an entity.
-
D.
compatibleBrand
Indicates that one brand is suitable for use with, or functions properly alongside, another brand.
-
E.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 29, 2026, 8:12 p.m.