Triple
T8486852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retry-After |
E200851
|
entity |
| Predicate | statusCodeCategory |
P2551
|
FINISHED |
| Object | commonly used with 4xx responses |
—
|
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: commonly used with 4xx responses | Statement: [Retry-After, statusCodeCategory, commonly used with 4xx responses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCodeCategory Context triple: [Retry-After, statusCodeCategory, commonly used with 4xx responses]
-
A.
categoryStatus
Indicates the current state or condition assigned to a category within a given system or context.
-
B.
usesStatusCodeClass
chosen
Indicates that one entity employs or relies on a particular class or range of status codes (e.g., HTTP status code classes) in its behavior or processing.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.