Triple
T9175245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/1.1 Range Requests |
E220182
|
entity |
| Predicate | serverResponseForUnsatisfiableRange |
P33257
|
FINISHED |
| Object | 416 Range Not Satisfiable |
—
|
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: 416 Range Not Satisfiable | Statement: [HTTP/1.1 Range Requests, serverResponseForUnsatisfiableRange, 416 Range Not Satisfiable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serverResponseForUnsatisfiableRange Context triple: [HTTP/1.1 Range Requests, serverResponseForUnsatisfiableRange, 416 Range Not Satisfiable]
-
A.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
B.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
C.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
D.
subrange
Indicates that one value or interval lies entirely within the bounds of another value or interval.
-
E.
nativeRange
Indicates the geographic area where an entity naturally occurs or originated without human introduction.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa2f9708190a955bf28a4f04004 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.