Triple
T10033267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COBOL |
E204900
|
entity |
| Predicate | hasStandard |
P1371
|
FINISHED |
| Object | COBOL-74 |
E204900
|
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: COBOL-74 | Statement: [COBOL, hasStandard, COBOL-74]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: COBOL-74 Context triple: [COBOL, hasStandard, COBOL-74]
-
A.
COBOL
chosen
COBOL is a long-established, English-like programming language primarily used for business, finance, and administrative systems on mainframes and enterprise platforms.
-
B.
IBM Enterprise COBOL
IBM Enterprise COBOL is IBM’s modern, optimized implementation of the COBOL programming language for developing and maintaining high-performance business applications on IBM mainframe systems.
-
C.
GnuCOBOL
GnuCOBOL is a free, open-source compiler that translates COBOL programs into C, enabling them to be compiled and run on modern systems.
-
D.
IBM 7090 FORTRAN compiler
The IBM 7090 FORTRAN compiler was an early high-level language compiler developed by IBM for its 7090 mainframe, widely used in the 1960s for scientific and engineering computing.
-
E.
PL/I-80
PL/I-80 is a microcomputer implementation of the PL/I programming language designed for 8-bit systems such as those running CP/M.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce47845c8190ab5696267fdedcad |
completed | April 2, 2026, 2:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a225e0c8190b87eb646cefa6a33 |
completed | April 5, 2026, 5:21 p.m. |
Created at: March 30, 2026, 8:54 p.m.