Triple
T29733236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2069 |
E752386
|
entity |
| Predicate | specifiesHeader |
P3703
|
FINISHED |
| Object | WWW-Authenticate |
—
|
NE NERFINISHED |
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: WWW-Authenticate | Statement: [RFC 2069, specifiesHeader, WWW-Authenticate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesHeader Context triple: [RFC 2069, specifiesHeader, WWW-Authenticate]
-
A.
belongsToHeader
Indicates that something is associated with, contained within, or conceptually grouped under a specific header.
-
B.
headerField
chosen
Indicates that one entity is a specific header field (such as a name–value pair) belonging to or defined within another entity, typically a message, request, or document header.
-
C.
usesHeaderStructure
Indicates that one entity organizes its content using a defined hierarchy of header elements or levels.
-
D.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
E.
headerTransport
Indicates that data or content is being transferred within or via the header portion of a message, request, or communication.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 7:43 p.m.