Triple
T28583960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timeout Detection and Recovery |
E723442
|
entity |
| Predicate | relatedErrorCode |
P5026
|
FINISHED |
| Object | 0x116 |
—
|
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: 0x116 | Statement: [Timeout Detection and Recovery, relatedErrorCode, 0x116]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedErrorCode Context triple: [Timeout Detection and Recovery, relatedErrorCode, 0x116]
-
A.
relatedCode
chosen
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
B.
relatedCodeDescription
Indicates that there is a descriptive explanation associated with a related code, clarifying its meaning or context.
-
C.
associatedFault
Indicates a relationship where a given entity is linked to, or occurs in connection with, a specific fault or error condition.
-
D.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
E.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: April 28, 2026, 4:16 a.m.