Triple
T9175232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/1.1 Range Requests |
E220182
|
entity |
| Predicate | supportsSingleRange |
P86640
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HTTP/1.1 Range Requests, supportsSingleRange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSingleRange Context triple: [HTTP/1.1 Range Requests, supportsSingleRange, true]
-
A.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
supportsBitpoolRange
Indicates that one entity is capable of handling or is compatible with a specified range of bitpool values used in an associated encoding or communication process.
-
D.
rangeCapability
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
E.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:23 p.m.