Triple
T30382288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony E |
E772862
|
entity |
| Predicate | hasCropFactor |
P169098
|
FINISHED |
| Object | 1.5x on APS-C bodies |
—
|
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: 1.5x on APS-C bodies | Statement: [Sony E, hasCropFactor, 1.5x on APS-C bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCropFactor Context triple: [Sony E, hasCropFactor, 1.5x on APS-C bodies]
-
A.
cropFactor
chosen
Indicates the ratio between a camera sensor’s dimensions and a reference format (typically 35mm/full-frame), expressing how much the field of view is effectively “cropped” compared to that standard.
-
B.
hasWideCamera
Indicates that an entity is equipped with or features a wide-angle camera.
-
C.
isCrop
Indicates that an entity functions as or is classified as an agricultural crop.
-
D.
hasLongFocalLength
Indicates that one entity possesses or is characterized by a focal length that is relatively long compared to a standard or reference.
-
E.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8 p.m.