Triple
T17598859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PostgreSQL documentation |
E428640
|
entity |
| Predicate | covers |
P1393
|
FINISHED |
| Object | PL/Tcl |
—
|
NE NERFINISHED |
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/Tcl | Statement: [PostgreSQL documentation, covers, PL/Tcl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PL/Tcl Context triple: [PostgreSQL documentation, covers, PL/Tcl]
-
A.
PL/Tcl
chosen
PL/Tcl is a procedural language extension for PostgreSQL that allows writing database functions and triggers using the Tcl scripting language.
-
B.
Tcl
Tcl (Tool Command Language) is a high-level, embeddable scripting language widely used for rapid prototyping, GUI development (often with Tk), and extending applications.
-
C.
TclOO
TclOO is an object-oriented extension to the Tcl programming language that provides a modern, flexible framework for defining and working with objects and classes.
-
D.
Jim Tcl
Jim Tcl is a lightweight, embeddable implementation of the Tcl scripting language designed for use in resource-constrained systems and applications.
-
E.
TLPL
TLPL is the ICAO airport code for Hewanorra International Airport, the main international gateway to Saint Lucia in the Caribbean.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.