Triple
T9175251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/1.1 Range Requests |
E220182
|
entity |
| Predicate | fallbackWhenIfRangeFails |
P64399
|
FINISHED |
| Object | 200 OK with full representation |
—
|
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: 200 OK with full representation | Statement: [HTTP/1.1 Range Requests, fallbackWhenIfRangeFails, 200 OK with full representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallbackWhenIfRangeFails Context triple: [HTTP/1.1 Range Requests, fallbackWhenIfRangeFails, 200 OK with full representation]
-
A.
fallbackTo
chosen
Indicates that when a primary option, method, or resource is unavailable or fails, an alternative one is used instead.
-
B.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
E.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
- 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.