Triple
T21727053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-10 |
E536299
|
entity |
| Predicate | notableLanguage |
P207
|
FINISHED |
| Object | MACRO-10 assembly language |
—
|
NE NERFINISHED |
How this triple was built (3 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: MACRO-10 assembly language | Statement: [PDP-10, notableLanguage, MACRO-10 assembly language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MACRO-10 assembly language Context triple: [PDP-10, notableLanguage, MACRO-10 assembly language]
-
A.
M4 macro processor
The M4 macro processor is a general-purpose macro processing language and tool commonly used in Unix-like systems for generating and transforming text, especially in build and configuration workflows.
-
B.
MACRO-11
MACRO-11 is the assembly language for DEC's PDP-11 minicomputers, widely used for low-level systems and application programming on RSX-11 and related operating systems.
-
C.
IBM High Level Assembler
IBM High Level Assembler is IBM’s advanced assembly language development environment for mainframe systems, providing powerful macro facilities, optimization features, and tooling support for low-level z/Architecture programming.
-
D.
MIDAS assembler
MIDAS assembler is a low-level assembly language and assembler originally developed at MIT for systems like the Incompatible Timesharing System, known for its powerful macro facilities and use in early AI and time-sharing research.
-
E.
PLAN (ICL 1900 assembly language)
PLAN (Programming LAnguage for the 1900) is the low-level assembly language used to write system and application software for ICL 1900 series mainframe computers.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MACRO-10 assembly language Target entity description: MACRO-10 assembly language is the low-level programming language used to write software for DEC's PDP-10 mainframe computers, offering direct control over the machine's architecture and instruction set.
-
A.
M4 macro processor
The M4 macro processor is a general-purpose macro processing language and tool commonly used in Unix-like systems for generating and transforming text, especially in build and configuration workflows.
-
B.
MACRO-11
MACRO-11 is the assembly language for DEC's PDP-11 minicomputers, widely used for low-level systems and application programming on RSX-11 and related operating systems.
-
C.
IBM High Level Assembler
IBM High Level Assembler is IBM’s advanced assembly language development environment for mainframe systems, providing powerful macro facilities, optimization features, and tooling support for low-level z/Architecture programming.
-
D.
MIDAS assembler
MIDAS assembler is a low-level assembly language and assembler originally developed at MIT for systems like the Incompatible Timesharing System, known for its powerful macro facilities and use in early AI and time-sharing research.
-
E.
PLAN (ICL 1900 assembly language)
PLAN (Programming LAnguage for the 1900) is the low-level assembly language used to write system and application software for ICL 1900 series mainframe computers.
- F. None of above. chosen
Provenance (2 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:48 p.m.