Triple

T11352164
Position Surface form Disambiguated ID Type / Status
Subject Joint Video Team E268862 entity
Predicate standardDeveloped P1371 FINISHED
Object H.264 E53638 NE 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: H.264 | Statement: [Joint Video Team, standardDeveloped, H.264]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: H.264
Context triple: [Joint Video Team, standardDeveloped, H.264]
  • A. H.264 chosen
    H.264 is a widely used video compression standard known for delivering high-quality video at relatively low bitrates, commonly employed in streaming, broadcasting, and video recording.
  • B. MPEG-4
    MPEG-4 is a multimedia compression and coding standard widely used for digital audio, video, and interactive media distribution over the internet and other networks.
  • C. H.265
    H.265, also known as High Efficiency Video Coding (HEVC), is a video compression standard designed to significantly reduce bandwidth and storage requirements compared to its predecessor H.264 while maintaining high visual quality.
  • D. MPEG-H
    MPEG-H is a family of ISO/IEC standards developed by MPEG for advanced audio and multimedia coding, including immersive and 3D audio applications.
  • E. H.263
    H.263 is a video compression standard developed primarily for low-bitrate communication such as video conferencing and early internet video applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aacbe18081909e5fadb50082dd96 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea24489081908fbf47fd2e6d709c completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e543a6e97481909dc77a553b217b4d completed April 19, 2026, 9:05 p.m.
Created at: April 8, 2026, 9:33 p.m.