Triple
T12682608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterBase |
E302985
|
entity |
| Predicate | supportsLanguage |
P2177
|
FINISHED |
| Object | SQL |
E5275
|
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: SQL | Statement: [InterBase, supportsLanguage, SQL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SQL Context triple: [InterBase, supportsLanguage, SQL]
-
A.
SQL
chosen
SQL (Structured Query Language) is a standardized programming language used to manage, query, and manipulate data in relational database management systems.
-
B.
DB
DB is the commonly used abbreviation for Deutsche Bahn, Germany’s national railway company and one of the largest rail operators in Europe.
-
C.
DB
DB is the standard abbreviation for "Deutsche Biographie," a major German biographical reference work documenting notable figures from German history and culture.
-
D.
DB
DB is the vehicle registration code assigned to Dâmbovița County in Romania, whose capital is Târgoviște.
-
E.
SQL API
SQL API is a query interface in Apache Flink that lets users define streaming and batch data processing logic using standard SQL syntax.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d68358819095bdaab8adf1dcf0 |
completed | April 10, 2026, 8:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671a733a48190b55d296573c86eaf |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:21 p.m.