Triple
T8486787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Location header |
E200850
|
entity |
| Predicate | usedWithStatusCode |
P33257
|
FINISHED |
| Object | 201 Created |
—
|
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: 201 Created | Statement: [Location header, usedWithStatusCode, 201 Created]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithStatusCode Context triple: [Location header, usedWithStatusCode, 201 Created]
-
A.
usesStatusCodeClass
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.
-
B.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
definesStatusCodeClass
Indicates that an entity specifies or determines the classification category to which a particular status code belongs.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
- 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.