Triple
T17559547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MariaDB Corporation |
E427663
|
entity |
| Predicate | offers |
P178
|
FINISHED |
| Object | MariaDB ColumnStore |
—
|
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: MariaDB ColumnStore | Statement: [MariaDB Corporation, offers, MariaDB ColumnStore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MariaDB ColumnStore Context triple: [MariaDB Corporation, offers, MariaDB ColumnStore]
-
A.
ColumnStore
chosen
ColumnStore is a columnar storage engine for MariaDB designed to support scalable, high-performance analytics and data warehousing workloads.
-
B.
MariaDB
MariaDB is an open-source relational database management system, forked from MySQL, known for its compatibility, performance, and community-driven development.
-
C.
Vertica
Vertica is a high-performance, column-oriented analytical database system designed for large-scale data warehousing and real-time analytics.
-
D.
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.
-
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.
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.