Triple
T12562487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Stonebraker |
E295382
|
entity |
| Predicate | founded |
P104
|
FINISHED |
| Object | VoltDB |
E991162
|
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: VoltDB | Statement: [Michael Stonebraker, founded, VoltDB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VoltDB Context triple: [Michael Stonebraker, founded, VoltDB]
-
A.
VoltDB
chosen
VoltDB is a high-performance, in-memory, distributed SQL database designed for real-time analytics and transaction processing at massive scale.
-
B.
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.
-
C.
CockroachDB
CockroachDB is a distributed SQL database designed for horizontal scalability, strong consistency, and high fault tolerance across multiple nodes and regions.
-
D.
Vertica
Vertica is a high-performance, column-oriented analytical database system designed for large-scale data warehousing and real-time analytics.
-
E.
RethinkDB
RethinkDB is an open-source, distributed NoSQL database designed for real-time applications by pushing live updates to clients as data changes.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95494ae1c81908b9ee14b8ef92a65 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65eb71c548190826d243a354bd01c |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 11:48 p.m.