Triple
T8993235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOS/VS |
E214839
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | Job Control Language |
E200570
|
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: Job Control Language | Statement: [DOS/VS, hasComponent, Job Control Language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Job Control Language Context triple: [DOS/VS, hasComponent, Job Control Language]
-
A.
Job Control Language
chosen
Job Control Language (JCL) is a scripting language used on IBM mainframe systems to define and control batch jobs and their execution.
-
B.
JCL
JCL is the standard set of pre-built classes and APIs that provide core functionality for Java programs, including utilities for data structures, I/O, networking, and more.
-
C.
FLOW-MATIC programming language
FLOW-MATIC programming language is an early English-like business data processing language developed in the 1950s that heavily influenced the design of COBOL.
-
D.
C shell
C shell is a Unix command-line interpreter known for its C-like syntax, interactive features, and scripting capabilities.
-
E.
Job Entry Subsystem 3
Job Entry Subsystem 3 (JES3) is an IBM mainframe component for managing and scheduling batch jobs, spooling, and input/output operations in z/OS environments.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6876583081909d936dc3c3152587 |
completed | April 1, 2026, 12:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd0cd2b948190947a26fe11ad81bf |
completed | April 3, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:04 p.m.