Triple
T4279288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL/Tcl |
E97111
|
entity |
| Predicate | usesLanguage |
P238
|
FINISHED |
| Object | Tcl |
E216043
|
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: Tcl | Statement: [PL/Tcl, usesLanguage, Tcl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tcl Context triple: [PL/Tcl, usesLanguage, Tcl]
-
A.
Tcl
chosen
Tcl (Tool Command Language) is a high-level, embeddable scripting language widely used for rapid prototyping, GUI development (often with Tk), and extending applications.
-
B.
PL/Tcl
PL/Tcl is a procedural language extension for PostgreSQL that allows writing database functions and triggers using the Tcl scripting language.
-
C.
Tcsh
Tcsh is an enhanced version of the C shell (csh) for Unix-like systems, featuring command-line editing, programmable completion, and other interactive conveniences.
-
D.
tk (macrolanguage)
tk (macrolanguage) is the ISO 639-1/2/3 code for the Turkmen language, a Turkic macrolanguage spoken primarily in Turkmenistan and surrounding regions.
-
E.
ARexx
ARexx is a REXX-based scripting language for the AmigaOS platform, commonly used to automate tasks and enable inter-application communication.
- 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.