Triple

T19111718
Position Surface form Disambiguated ID Type / Status
Subject Raft consensus algorithm E467805 entity
Predicate usedIn P98 FINISHED
Object TiKV NE NERFINISHED

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: TiKV | Statement: [Raft consensus algorithm, usedIn, TiKV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TiKV
Context triple: [Raft consensus algorithm, usedIn, TiKV]
  • A. TiKV chosen
    TiKV is an open-source, distributed transactional key-value database designed for horizontal scalability and strong consistency, often used as the storage layer for cloud-native applications.
  • B. CockroachDB
    CockroachDB is a distributed SQL database designed for horizontal scalability, strong consistency, and high fault tolerance across multiple nodes and regions.
  • C. RocksDB
    RocksDB is a high-performance, embeddable key–value store developed by Facebook, optimized for fast storage on flash and solid-state drives using a Log-Structured Merge-Tree (LSM) architecture.
  • D. BSTDB
    BSTDB is a regional multilateral development bank that finances projects to promote economic development and cooperation among Black Sea region member countries.
  • E. ScyllaDB
    ScyllaDB is a high-performance, distributed NoSQL database designed as a drop-in replacement for Apache Cassandra, optimized for low latency and high throughput.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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.
Created at: April 10, 2026, 12:04 p.m.