Triple

T1672131
Position Surface form Disambiguated ID Type / Status
Subject MariaDB E36148 entity
Predicate supportsStorageEngine P203 FINISHED
Object InnoDB E97106 NE FINISHED

How this triple was built (3 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: [MariaDB, supportsStorageEngine, InnoDB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: InnoDB
Context triple: [MariaDB, supportsStorageEngine, 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. 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.
  • 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. MySQL HeatWave
    MySQL HeatWave is a fully managed, in-memory query acceleration and analytics engine integrated with MySQL to deliver high-performance OLTP and OLAP processing on the same database service.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsStorageEngine
Context triple: [MariaDB, supportsStorageEngine, InnoDB]
  • A. supportsDatastoreType
    Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
  • B. storageOption
    Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
  • C. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • D. supportsTransactions
    Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
  • E. supportsUse
    Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
  • F. None of above.

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_69a8861286808190939afff3ce8ee31e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab272a653481908f48aa1eed5de8a4 completed March 6, 2026, 7:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad71b0cde08190a210cf387459e9ad completed March 8, 2026, 12:55 p.m.
PD Predicate disambiguation batch_69aa61b2f6288190b2348ef7d7e4672d completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:29 p.m.