Triple
T4279225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL/pgSQL |
E97109
|
entity |
| Predicate | languageName |
P13426
|
FINISHED |
| Object | PL/pgSQL |
E97109
|
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: PL/pgSQL | Statement: [PL/pgSQL, languageName, PL/pgSQL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PL/pgSQL Context triple: [PL/pgSQL, languageName, PL/pgSQL]
-
A.
PL/pgSQL
chosen
PL/pgSQL is PostgreSQL’s procedural extension of SQL that allows writing stored functions and triggers with control structures like variables, loops, and conditionals.
-
B.
PL/SQL
PL/SQL is Oracle's proprietary procedural extension to SQL, used for writing stored procedures, functions, and complex database logic within Oracle Database.
-
C.
PostgreSQL
PostgreSQL is a powerful open-source relational database management system known for its robustness, extensibility, and strong standards compliance.
-
D.
PL/Python
PL/Python is a procedural language extension for PostgreSQL that allows writing database functions and triggers in the Python programming language.
-
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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350367da48190b735deef9b5d2d2e |
completed | March 12, 2026, 11:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b7b708b481908c1683741f84ee55 |
completed | March 14, 2026, 7:32 p.m. |
Created at: March 12, 2026, 11:07 p.m.