Triple
T37215396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.266 |
E922721
|
entity |
| Predicate | usesCodingStructure |
P28140
|
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: [H.266, usesCodingStructure, block-based hybrid video coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodingStructure Context triple: [H.266, usesCodingStructure, block-based hybrid video coding]
-
A.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
-
B.
codeStructureDescription
Indicates that one entity provides a textual or symbolic explanation of the organization, components, or layout of a piece of code represented by another entity.
-
C.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
D.
programmingStyle
Indicates the particular approach, methodology, or paradigm an entity uses when writing or organizing code.
-
E.
encodingStructure
chosen
Indicates the structural scheme or format used to encode information or data.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 3, 2026, 4:15 p.m.