Triple
T17559648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innobase Oy |
E427666
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | InnoDB |
—
|
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: InnoDB | Statement: [Innobase Oy, product, InnoDB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: InnoDB Context triple: [Innobase Oy, product, InnoDB]
-
A.
InnoDB storage engine
chosen
InnoDB storage engine is a widely used transactional storage engine for MySQL that provides ACID compliance, row-level locking, and crash recovery for reliable, high-performance database operations.
-
B.
TokuDB
TokuDB is a high-performance storage engine for MySQL and MariaDB designed for large-scale, write-intensive workloads using Fractal Tree indexing to improve compression and insertion speed.
-
C.
MyISAM storage engine
The MyISAM storage engine is a legacy MySQL table format known for fast read performance, simple design, and lack of transactional and foreign key support.
-
D.
Percona XtraDB
Percona XtraDB is an enhanced, high-performance fork of the InnoDB storage engine used in MySQL and MariaDB, optimized for improved scalability, reliability, and performance.
-
E.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 5:50 a.m.