Triple

T19112142
Position Surface form Disambiguated ID Type / Status
Subject Practical Byzantine Fault Tolerance E467813 entity
Predicate typeOfFaultTolerance P134467 FINISHED
Object Byzantine fault tolerance 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: Byzantine fault tolerance | Statement: [Practical Byzantine Fault Tolerance, typeOfFaultTolerance, Byzantine fault tolerance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfFaultTolerance
Context triple: [Practical Byzantine Fault Tolerance, typeOfFaultTolerance, Byzantine fault tolerance]
  • A. typeOfFaulting
    Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
  • B. typeOfFailure
    Indicates the specific kind or category of failure that occurred in relation to an entity or process.
  • C. typeOfCluster
    Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
  • D. typeOfResistance
    Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
  • E. persistenceType
    Indicates the manner or mode in which something continues to exist, endure, or remain over time.
  • F. None of above. chosen

Provenance (4 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_69d8dd06a26481908039e2a1bae8c597 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e394969c81909d09b2300ea0e041 completed April 20, 2026, 8:28 a.m.
PD Predicate disambiguation batch_69e4b9ac41848190afd0f33b42cebe99 completed April 19, 2026, 11:17 a.m.
PDg Predicate description generation batch_69e4bfe8a06081909fd5c28a33e9f218 completed April 19, 2026, 11:43 a.m.
Created at: April 10, 2026, 12:04 p.m.