Triple
T21191193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authentication Header |
E522213
|
entity |
| Predicate | statusInRFC4302 |
P8040
|
FINISHED |
| Object | Internet Standard Track protocol |
—
|
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: Internet Standard Track protocol | Statement: [Authentication Header, statusInRFC4302, Internet Standard Track protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRFC4302 Context triple: [Authentication Header, statusInRFC4302, Internet Standard Track protocol]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
statusInHTTP2
Indicates the HTTP/2 status or condition associated with a request/response exchange, such as success, error, or protocol-specific state.
-
C.
statusInHTTP3
Indicates the HTTP/3 protocol status or condition associated with a given resource, request, or connection.
-
D.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.