Triple
T12682724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBArtisan |
E302987
|
entity |
| Predicate | supportsDatabaseType |
P11254
|
FINISHED |
| Object | relational database management system |
—
|
LITERAL 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: relational database management system | Statement: [DBArtisan, supportsDatabaseType, relational database management system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDatabaseType Context triple: [DBArtisan, supportsDatabaseType, relational database management system]
-
A.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
B.
supportsDatabaseAbstraction
Indicates that one entity provides or enables a database abstraction layer for another, allowing interaction with databases independently of specific database implementations.
-
C.
databaseType
Indicates the specific kind or category of database technology associated with an entity.
-
D.
supportsDatastoreType
chosen
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
-
E.
supportsDatabaseAbstractionLayer
Indicates that one entity provides or is compatible with a database abstraction layer used by another entity for interacting 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d68358819095bdaab8adf1dcf0 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.