Triple
T33027346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACCT |
E845076
|
entity |
| Predicate | statusCodeOnFailure |
P175713
|
FINISHED |
| Object | 530 |
—
|
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: 530 | Statement: [ACCT, statusCodeOnFailure, 530]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCodeOnFailure Context triple: [ACCT, statusCodeOnFailure, 530]
-
A.
failureResponseCodeExample
chosen
Indicates the example HTTP status code that should be returned when the related operation fails.
-
B.
statusInHTTP3
Indicates the HTTP/3 protocol status or condition associated with a given resource, request, or connection.
-
C.
statusInHTTP2
Indicates the HTTP/2 status or condition associated with a request/response exchange, such as success, error, or protocol-specific state.
-
D.
errorStatusSemantics
Indicates how the meaning or interpretation of an error status value should be understood within a given context or system.
-
E.
definesStatusCode
Indicates that one entity specifies or assigns the status code used to represent the condition or outcome of another entity or 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:23 a.m.