Triple
T9002141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VC-1 |
E215061
|
entity |
| Predicate | videoCodingType |
P54493
|
FINISHED |
| Object | block-based hybrid video coding |
—
|
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: block-based hybrid video coding | Statement: [VC-1, videoCodingType, block-based hybrid video coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoCodingType Context triple: [VC-1, videoCodingType, block-based hybrid video coding]
-
A.
videoEncoding
chosen
Indicates that one entity is used to encode, compress, or transform video data into a particular digital format or representation for another entity.
-
B.
audioCodingType
Indicates the specific method or standard used to encode or compress an audio signal.
-
C.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
D.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
-
E.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.