Triple
T19636667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine fault tolerance |
E471415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consensus property |
C20337
|
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: consensus property Context triple: [Byzantine fault tolerance, instanceOf, consensus property]
-
A.
fault-tolerant consensus protocol
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.
conservation property
A conservation property is a characteristic of a physical quantity that remains constant within an isolated system despite internal changes or transformations.
-
C.
distributed consensus algorithm
A distributed consensus algorithm is a protocol that enables a group of independent, networked nodes to reliably agree on a single shared value or state, even in the presence of failures or unreliable communication.
-
D.
confluence property
chosen
The confluence property is a characteristic of a rewriting or transition system where, if a state can evolve into two different states, there always exists a further sequence of steps from each of those states that leads to a common successor state.
-
E.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:44 p.m.