Triple
T33436028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP cookie |
E856240
|
entity |
| Predicate | setByHeader |
P158375
|
FINISHED |
| Object | Set-Cookie |
—
|
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: Set-Cookie | Statement: [HTTP cookie, setByHeader, Set-Cookie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setByHeader Context triple: [HTTP cookie, setByHeader, Set-Cookie]
-
A.
belongsToHeader
Indicates that something is associated with, contained within, or conceptually grouped under a specific header.
-
B.
headerField
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.
headerValues
Indicates that one entity specifies or provides the set of values associated with a particular header in a structured message or data record.
-
D.
addsHeaderType
chosen
Indicates that one entity appends or associates a specific header type to another entity, such as a message, request, or data structure.
-
E.
usesHeadFrom
Indicates that one entity employs or incorporates the head component of another entity in its structure or function.
- 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_69f6e4857f3c819086399a37e954c6e9 |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.