Triple
T28330089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percona XtraDB |
E717515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | InnoDB fork |
C15505
|
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: InnoDB fork Context triple: [Percona XtraDB, instanceOf, InnoDB fork]
-
A.
MySQL storage engine
chosen
A MySQL storage engine is a modular component that defines how data is stored, indexed, and retrieved for tables within a MySQL database.
-
B.
OpenBSD fork
An OpenBSD fork is a derivative operating system project that originates from the OpenBSD codebase, maintaining its core security-focused and correctness-driven design while evolving independently under separate governance and development priorities.
-
C.
file-based database engine
A file-based database engine is a lightweight data management system that stores and retrieves structured data directly from local files without requiring a separate database server process.
-
D.
sharding engine
A sharding engine is a system component that automatically partitions and routes data across multiple database shards to improve scalability, performance, and availability while presenting a unified logical view.
-
E.
PostgreSQL subsystem
A PostgreSQL subsystem is a cohesive internal component or module within the PostgreSQL database architecture that provides a specific set of functionalities—such as storage, query processing, or transaction management—to support overall database operations.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:31 a.m.