Triple
T29503782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic |
E748454
|
entity |
| Predicate | responseHeaderUsed |
P3703
|
FINISHED |
| Object | WWW-Authenticate 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: WWW-Authenticate header | Statement: [Basic, responseHeaderUsed, WWW-Authenticate header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseHeaderUsed Context triple: [Basic, responseHeaderUsed, WWW-Authenticate header]
-
A.
usesResponseCode
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
B.
responseUnit
Indicates a unit or entity that provides or carries out a response in relation to another entity or event.
-
C.
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.
-
D.
responseTermination
Indicates that a response, process, or interaction has been brought to an end, either normally or due to some terminating condition.
-
E.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:26 p.m.