Triple

T8486912
Position Surface form Disambiguated ID Type / Status
Subject QPACK E200852 entity
Predicate encoderRole P49872 FINISHED
Object maintains dynamic table and sends header instructions 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: maintains dynamic table and sends header instructions | Statement: [QPACK, encoderRole, maintains dynamic table and sends header instructions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: encoderRole
Context triple: [QPACK, encoderRole, maintains dynamic table and sends header instructions]
  • A. encodingRole chosen
    Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
  • B. speakerRole
    Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
  • C. mediaRole
    Indicates the specific function, capacity, or position an entity holds in relation to a media item (such as creator, editor, performer, or distributor).
  • D. roleInVox
    Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
  • E. sonRole
    Indicates that one entity holds the role or relationship of a son with respect to another entity.
  • 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_69ca831d7b148190a6e32c1de43ab13b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe53c4d608190a766c0e919a4b96f completed March 31, 2026, 3:16 p.m.
PD Predicate disambiguation batch_69cbd107633c8190a36ba50e07876918 completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:13 p.m.