Triple
T31008788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7S II |
E790149
|
entity |
| Predicate | 4KRecordingMethod |
P15057
|
FINISHED |
| Object | internal 4K recording |
—
|
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: internal 4K recording | Statement: [Sony α7S II, 4KRecordingMethod, internal 4K recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 4KRecordingMethod Context triple: [Sony α7S II, 4KRecordingMethod, internal 4K recording]
-
A.
supports4KVideoRecording
Indicates that the subject is capable of recording video at 4K (Ultra HD) resolution.
-
B.
recordingMethod
chosen
Indicates the technique or process used to capture or record something (such as data, audio, or video).
-
C.
recordingMode
Indicates the method or configuration by which something is recorded, such as how data, audio, or video capture is performed.
-
D.
supportsDolbyVisionHDRRecording
Indicates that the subject is capable of recording video content using the Dolby Vision high dynamic range (HDR) format.
-
E.
4KRecommendedBandwidth
Indicates the amount of network bandwidth that is recommended to reliably stream or deliver 4K (ultra-high-definition) content.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.