Triple

T17417237
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC 23008-2 E423518 entity
Predicate developedBy P73 FINISHED
Object JCT-VC NE NERFINISHED

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: JCT-VC | Statement: [ISO/IEC 23008-2, developedBy, JCT-VC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: JCT-VC
Context triple: [ISO/IEC 23008-2, developedBy, JCT-VC]
  • A. JVT
    JVT is the Joint Video Team, a collaborative standards group formed by ITU-T and ISO/IEC to develop the H.264/AVC video compression standard.
  • B. ISO/IEC 14496
    ISO/IEC 14496 is an international standard better known as MPEG-4, defining methods for coding audio-visual objects for multimedia, web, and broadcast applications.
  • C. ITU-T Video Coding Experts Group chosen
    The ITU-T Video Coding Experts Group is an international standards body within the ITU responsible for developing widely used video compression standards such as H.264/AVC and H.265/HEVC.
  • D. H.263
    H.263 is a video compression standard developed primarily for low-bitrate communication such as video conferencing and early internet video applications.
  • E. Versatile Video Coding
    Versatile Video Coding is a next-generation video compression standard designed to significantly improve coding efficiency over its predecessors for applications ranging from low-bitrate streaming to ultra-high-definition video.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44233c7888190a4d2aa703b206851 completed April 19, 2026, 2:47 a.m.
Created at: April 10, 2026, 5:46 a.m.