Triple

T270944
Position Surface form Disambiguated ID Type / Status
Subject HTTP/3 E5630 entity
Predicate avoidsProblem P3847 FINISHED
Object head-of-line blocking at transport layer 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: head-of-line blocking at transport layer | Statement: [HTTP/3, avoidsProblem, head-of-line blocking at transport layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: avoidsProblem
Context triple: [HTTP/3, avoidsProblem, head-of-line blocking at transport layer]
  • A. prohibits
    Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
  • B. addressesIssue chosen
    Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
  • C. doesNot
    Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
  • D. excludes
    Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
  • E. warnsAbout
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • 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_69a25853594c8190b05ec3a586ec88bf completed Feb. 28, 2026, 2:52 a.m.
NER Named-entity recognition batch_69a25e69a9248190b9e7959b43223baa completed Feb. 28, 2026, 3:18 a.m.
PD Predicate disambiguation batch_69a25b721180819080d43c43fcbccf87 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:57 a.m.