Triple
T10032294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If-None-Match |
E204878
|
entity |
| Predicate | responseStatusOnMatchGET |
P33257
|
FINISHED |
| Object | 304 Not Modified |
—
|
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: 304 Not Modified | Statement: [If-None-Match, responseStatusOnMatchGET, 304 Not Modified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseStatusOnMatchGET Context triple: [If-None-Match, responseStatusOnMatchGET, 304 Not Modified]
-
A.
statusMatchWith
Indicates that two entities share the same status or that one entity’s status corresponds to another according to a defined matching rule.
-
B.
statusMatchAvailable
Indicates that the current status of an entity matches a condition or value that qualifies it as available.
-
C.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
D.
returnStatus
Indicates the current outcome or condition of a previously initiated return action or process.
-
E.
respondentStatus
Indicates the current role, condition, or state of a respondent in relation to a survey, inquiry, or legal/administrative process.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce461d6481908cc8f968856e0337 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.