Triple
T29863861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mod_deflate |
E758394
|
entity |
| Predicate | addsHeader |
P158375
|
FINISHED |
| Object | Content-Encoding |
—
|
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: Content-Encoding | Statement: [mod_deflate, addsHeader, Content-Encoding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsHeader Context triple: [mod_deflate, addsHeader, Content-Encoding]
-
A.
addsHeaderType
chosen
Indicates that one entity appends or associates a specific header type to another entity, such as a message, request, or data structure.
-
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.
belongsToHeader
Indicates that something is associated with, contained within, or conceptually grouped under a specific header.
-
D.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
E.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67687612c8190b4781cfe3898bf7f |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:50 p.m.