Triple
T28442792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokutek |
E715757
|
entity |
| Predicate | supportedDatabase |
P105447
|
FINISHED |
| Object | MySQL |
—
|
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: MySQL | Statement: [Tokutek, supportedDatabase, MySQL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedDatabase Context triple: [Tokutek, supportedDatabase, MySQL]
-
A.
supportsEnterpriseDatabases
Indicates that something is capable of working with or being compatible with enterprise-grade database systems.
-
B.
supportsDatabaseConnectivity
chosen
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
C.
usesDatabases
Indicates that an entity employs one or more databases as part of its operations, functionality, or processes.
-
D.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
E.
supportsDatabaseAbstraction
Indicates that one entity provides or enables a database abstraction layer for another, allowing interaction with databases independently of specific database implementations.
- F. None of above.
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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: April 28, 2026, 1:47 a.m.