Triple
T30588803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-1000XM2 |
E778591
|
entity |
| Predicate | codecSupport |
P64032
|
FINISHED |
| Object | SBC |
—
|
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: SBC | Statement: [Sony WI-1000XM2, codecSupport, SBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codecSupport Context triple: [Sony WI-1000XM2, codecSupport, SBC]
-
A.
usesCodec
chosen
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
B.
supportsH264
Indicates that one entity provides compatibility with, or the ability to encode/decode or process, H.264 video for another entity.
-
C.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) for another entity.
-
D.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68978f62481909563f733a8d902db |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.