Triple
T33433315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Referer HTTP header |
E856186
|
entity |
| Predicate | usedInProtocolVersion |
P75898
|
FINISHED |
| Object | HTTP/1.0 |
—
|
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/1.0 | Statement: [Referer HTTP header, usedInProtocolVersion, HTTP/1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProtocolVersion Context triple: [Referer HTTP header, usedInProtocolVersion, HTTP/1.0]
-
A.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
B.
usedInVersionRange
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
C.
relatedToProtocolVersion
chosen
Indicates a relationship where something is associated with, governed by, or dependent on a specific protocol version.
-
D.
specifiesProtocolVersion
Indicates that an entity defines or sets the particular protocol version to be used in a communication or interaction.
-
E.
usesProtocolValue
Indicates that one entity operates according to, or communicates using, a specified protocol value.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 1, 2026, 1:36 a.m.