Triple
T7928221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSET |
E184120
|
entity |
| Predicate | serverResponseOnFailure |
P33257
|
FINISHED |
| Object | -ERR |
—
|
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: -ERR | Statement: [RSET, serverResponseOnFailure, -ERR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serverResponseOnFailure Context triple: [RSET, serverResponseOnFailure, -ERR]
-
A.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
B.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
D.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
E.
UNResponse
Indicates that an entity issues, represents, or embodies an official response, action, or position taken by the United Nations regarding another entity or situation.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.