Triple
T306745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/2 |
E6319
|
entity |
| Predicate | cleartextUpgradeMechanism |
P3705
|
FINISHED |
| Object | HTTP Upgrade header |
—
|
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: HTTP Upgrade header | Statement: [HTTP/2, cleartextUpgradeMechanism, HTTP Upgrade header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleartextUpgradeMechanism Context triple: [HTTP/2, cleartextUpgradeMechanism, HTTP Upgrade header]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
transitionMechanismUsedWith
chosen
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
C.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
-
E.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.