Triple
T35140875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TADOQuery |
E1014698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ADO data access component |
C32342
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ADO data access component Context triple: [TADOQuery, instanceOf, ADO data access component]
-
A.
database access component
A database access component is a software module responsible for establishing connections, executing queries, and managing data exchange between an application and its underlying database systems.
-
B.
Delphi VCL data-access component
chosen
A Delphi VCL data-access component is a reusable visual or non-visual class that encapsulates database connectivity, querying, and data manipulation logic for use within Delphi’s Visual Component Library applications.
-
C.
ODBC component
An ODBC component is a software module that enables applications to access and manipulate data in diverse database management systems through the standardized Open Database Connectivity (ODBC) interface.
-
D.
data access API
A data access API is an interface that provides standardized methods for applications to create, read, update, and delete data from underlying storage systems while abstracting away implementation details.
-
E.
Object–relational mapping tool
An object–relational mapping tool is a software library or framework that automatically maps objects in application code to rows in a relational database, allowing developers to work with data using object-oriented paradigms instead of SQL.
- F. None of above.
Provenance (1 batch)
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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.