Triple
T33027383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDUP |
E845077
|
entity |
| Predicate | responseCodeOnFailure |
P175713
|
FINISHED |
| Object | 500 |
—
|
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: 500 | Statement: [CDUP, responseCodeOnFailure, 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseCodeOnFailure Context triple: [CDUP, responseCodeOnFailure, 500]
-
A.
failureResponseCodeExample
chosen
Indicates the example HTTP status code that should be returned when the related operation fails.
-
B.
usesResponseCode
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
returnValueOnFailure
Indicates the value that should be produced or returned when the associated operation or process fails.
-
D.
failureReturn
Indicates that an operation or process results in an unsuccessful outcome and returns a corresponding failure value or status.
-
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:23 a.m.