Triple
T30481863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R5 |
E775608
|
entity |
| Predicate | videoInternal10bit |
P171079
|
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, videoInternal10bit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoInternal10bit Context triple: [Canon EOS R5, videoInternal10bit, true]
-
A.
hasHDMIPort
Indicates that one entity (typically a device) is equipped with an HDMI port that can be used to connect to another entity.
-
B.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
C.
HDRVideo
Indicates that the video content is encoded or presented using High Dynamic Range, providing an expanded range of brightness and color compared to standard video.
-
D.
supportsDolbyVisionHDRRecording
Indicates that the subject is capable of recording video content using the Dolby Vision high dynamic range (HDR) format.
-
E.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) for another entity.
- 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_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:12 p.m.