Triple
T2561532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OLE DB |
E57250
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | JDBC |
E56740
|
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: JDBC | Statement: [OLE DB, relatedTo, JDBC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JDBC Context triple: [OLE DB, relatedTo, JDBC]
-
A.
JDBC
chosen
JDBC (Java Database Connectivity) is a Java-based API that enables applications to connect to and interact with relational databases in a standardized way.
-
B.
javax.sql
javax.sql is a Java package that provides extended JDBC support for database access, including connection pooling, distributed transactions, and rowset implementations.
-
C.
ODBC
ODBC (Open Database Connectivity) is a standard API that enables applications to access and query data from a wide variety of relational and non-relational database management systems using a common interface.
-
D.
DriverManager
DriverManager is a core JDBC utility class in Java that manages a list of database drivers and establishes connections to databases based on provided URLs and credentials.
-
E.
SQL
SQL (Structured Query Language) is a standardized programming language used to manage, query, and manipulate data in relational database management systems.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd336183c819084ed7de8ccc4c548 |
completed | March 7, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af83a4f6788190be268076838711df |
completed | March 10, 2026, 2:36 a.m. |
Created at: March 6, 2026, 9:48 p.m.