Triple
T4279313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL/Tcl |
E97111
|
entity |
| Predicate | languageHandlerFunction |
P55180
|
FINISHED |
| Object | pltcl_call_handler |
—
|
LITERAL 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: pltcl_call_handler | Statement: [PL/Tcl, languageHandlerFunction, pltcl_call_handler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageHandlerFunction Context triple: [PL/Tcl, languageHandlerFunction, pltcl_call_handler]
-
A.
handledLanguage
Indicates that an entity has processed, used, or otherwise dealt with a particular language in some context.
-
B.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
C.
languageView
Indicates a relationship where one entity views, interprets, or presents another entity through the lens of a particular language or linguistic perspective.
-
D.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
E.
languageName
Indicates the specific name assigned to a language in the relationship.
- F. None of above. chosen
Provenance (4 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. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.