Triple
T31583213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MACRO-11 |
E805878
|
entity |
| Predicate | inputTo |
P132538
|
FINISHED |
| Object | PDP-11 assembler |
—
|
LITERAL 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: PDP-11 assembler | Statement: [MACRO-11, inputTo, PDP-11 assembler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputTo Context triple: [MACRO-11, inputTo, PDP-11 assembler]
-
A.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
B.
inputIs
chosen
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
C.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
D.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
E.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
- F. None of above.
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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80b14308190aa4cb44b8c730611 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:24 p.m.