Triple
T27888789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zab protocol |
E705296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crash-recovery protocol |
C41036
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: crash-recovery protocol Context triple: [Zab protocol, instanceOf, crash-recovery protocol]
-
A.
fault-tolerant consensus protocol
chosen
A fault-tolerant consensus protocol is a distributed algorithm that enables a group of nodes to reliably agree on a shared state or value even when some nodes fail or behave maliciously.
-
B.
cluster-wide lock manager
A cluster-wide lock manager is a distributed coordination component that provides mutually exclusive access to shared resources across all nodes in a cluster, ensuring consistency and preventing conflicting operations.
-
C.
cascade
A cascade is a sequence of events, processes, or elements in which each step triggers or influences the next, often amplifying effects as they progress.
-
D.
storage protocol
A storage protocol is a defined set of rules and procedures that govern how data is transmitted, accessed, and managed between storage devices and host systems.
-
E.
disaster recovery solution
A disaster recovery solution is a comprehensive system of tools, processes, and policies designed to quickly restore critical IT services and data after disruptive events, minimizing downtime and business impact.
- F. None of above.
Provenance (1 batch)
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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:34 p.m.