Triple

T10033252
Position Surface form Disambiguated ID Type / Status
Subject COBOL E204900 entity
Predicate influenced P9 FINISHED
Object PL/I E129068 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: PL/I | Statement: [COBOL, influenced, PL/I]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PL/I
Context triple: [COBOL, influenced, PL/I]
  • A. PL/I chosen
    PL/I is a high-level programming language developed by IBM in the 1960s that combines features from scientific, business, and systems programming languages into a single, general-purpose language.
  • B. 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.
  • C. BCPL
    BCPL (Basic Combined Programming Language) is an early, typeless systems programming language developed in the 1960s that significantly influenced the design of the C programming language.
  • D. Algol 68C
    Algol 68C is a compiler implementation of the Algol 68 programming language, designed to translate its advanced structured constructs into executable machine code.
  • E. Algol 68
    Algol 68 is a high-level, structured programming language from the ALGOL family, notable for its orthogonal design and influence on many later languages.
  • 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_69d282478578819085ca00fe140bb6c1 completed April 5, 2026, 3:39 p.m.
Created at: March 30, 2026, 8:54 p.m.