Triple
T30481851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R5 |
E775608
|
entity |
| Predicate | hasInBodyImageStabilization |
P17639
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Canon EOS R5, hasInBodyImageStabilization, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInBodyImageStabilization Context triple: [Canon EOS R5, hasInBodyImageStabilization, true]
-
A.
hasOpticalImageStabilization
chosen
Indicates that a device or component includes a feature that reduces image blur caused by camera movement during capture.
-
B.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
C.
hasWideCamera
Indicates that an entity is equipped with or features a wide-angle camera.
-
D.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
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.
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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: April 29, 2026, 8:12 p.m.