Triple
T27657744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R7 (program counter) |
E697037
|
entity |
| Predicate | writableBy |
P93404
|
FINISHED |
| Object | PDP-11 software via control-flow instructions |
—
|
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 software via control-flow instructions | Statement: [R7 (program counter), writableBy, PDP-11 software via control-flow instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writableBy Context triple: [R7 (program counter), writableBy, PDP-11 software via control-flow instructions]
-
A.
writable
chosen
Indicates that one entity has permission or capability to modify or write data to another entity.
-
B.
writableByConsumers
Indicates that the target resource can be modified or written to by consumer entities (such as end users or client applications).
-
C.
writesTo
Indicates that one entity produces and records information, data, or content into another entity as a destination or storage target.
-
D.
canBeWrittenIn
Indicates that something is capable of being expressed, encoded, or represented using a particular language, notation, or medium.
-
E.
isEditableByUser
Indicates that a given item or resource can be modified or updated by a specified user.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f631dad37c8190ab1b5918ad8a928a |
completed | May 2, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:35 p.m.