Triple
T2629299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortran |
E59594
|
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: [Fortran, influenced, PL/I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PL/I Context triple: [Fortran, 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.
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.
-
C.
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.
-
D.
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.
-
E.
Algol 68S
Algol 68S is a simplified subset of the Algol 68 programming language designed to make the language easier to implement and use.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8c452508190b02e1630d725497a |
completed | March 7, 2026, 7:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af90a44a348190b8b49b37418dd94b |
completed | March 10, 2026, 3:31 a.m. |
Created at: March 6, 2026, 9:50 p.m.