Triple
T7858441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPX/SPX |
E182433
|
entity |
| Predicate | errorControl |
P3685
|
FINISHED |
| Object | SPX error recovery |
—
|
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: SPX error recovery | Statement: [IPX/SPX, errorControl, SPX error recovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorControl Context triple: [IPX/SPX, errorControl, SPX error recovery]
-
A.
errorTerm
Indicates the specific discrepancy or residual value that quantifies the difference between an observed outcome and its predicted or true value in a model or calculation.
-
B.
errorRecovery
chosen
Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
-
C.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
D.
errorPhase
Indicates the specific stage or phase in a process or workflow during which an error occurred.
-
E.
errorHandlingModel
Indicates how a system or component manages, responds to, and recovers from errors or exceptional conditions during operation.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a787c8c8190bcd9ed76cc7aa4c5 |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.