Triple
T33186447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6797 |
E849481
|
entity |
| Predicate | definesHeaderFieldName |
P14546
|
FINISHED |
| Object | Strict-Transport-Security |
—
|
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: Strict-Transport-Security | Statement: [RFC 6797, definesHeaderFieldName, Strict-Transport-Security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHeaderFieldName Context triple: [RFC 6797, definesHeaderFieldName, Strict-Transport-Security]
-
A.
definesHeader
Indicates that one entity serves as the header or defining heading for another entity.
-
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.
definesField
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
D.
fieldName
chosen
Indicates the specific name or label assigned to a field within a data structure, form, or record.
-
E.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 1:29 a.m.