Triple
T1672134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MariaDB |
E36148
|
entity |
| Predicate | supportsStorageEngine |
P203
|
FINISHED |
| Object | MyISAM |
E100301
|
NE 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: MyISAM | Statement: [MariaDB, supportsStorageEngine, MyISAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MyISAM Context triple: [MariaDB, supportsStorageEngine, MyISAM]
-
A.
MyISAM storage engine
chosen
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.
-
B.
InnoDB storage engine
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.
-
C.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
-
D.
MySQL
MySQL is a widely used open-source relational database management system known for its reliability, performance, and role in powering many web applications and services.
-
E.
B-tree
A B-tree is a self-balancing tree data structure that maintains sorted data and allows efficient insertion, deletion, and search operations, commonly used to implement database indexes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abaffad4748190995fec39bc8d7a1f |
completed | March 7, 2026, 4:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad71b0cde08190a210cf387459e9ad |
completed | March 8, 2026, 12:55 p.m. |
Created at: March 4, 2026, 7:29 p.m.