Triple
T9611718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP-8 |
E232116
|
entity |
| Predicate | addressSpaceExpandableTo |
P31521
|
FINISHED |
| Object | 32K words |
—
|
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: 32K words | Statement: [PDP-8, addressSpaceExpandableTo, 32K words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressSpaceExpandableTo Context triple: [PDP-8, addressSpaceExpandableTo, 32K words]
-
A.
addressSpaceSize
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
B.
ramExpandableTo
chosen
Indicates that a device’s RAM can be increased from its current capacity up to a specified maximum amount.
-
C.
expandableTo
Indicates that one entity can be extended, enlarged, or developed to become or accommodate another entity.
-
D.
addressAllocation
Indicates the assignment or reservation of an address (such as an IP or memory address) for use by a specific entity or resource.
-
E.
expandsTo
Indicates that one entity unfolds, develops, or is elaborated into another, typically more detailed or extensive, representation or form.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a87764481909ab96cd2ab96d14b |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:09 p.m.