Triple
T10208198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Strict Transport Security specification |
E242258
|
entity |
| Predicate | appliesWhen |
P1129
|
FINISHED |
| Object | user agent has seen a valid HSTS header for the host |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: user agent has seen a valid HSTS header for the host | Statement: [HTTP Strict Transport Security specification, appliesWhen, user agent has seen a valid HSTS header for the host]
Provenance (2 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d395f8e2b881909c51f8210f09cd4f |
completed | April 6, 2026, 11:16 a.m. |
Created at: April 6, 2026, 10:57 a.m.