Triple
T6567094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honeywell 316 minicomputer |
E153934
|
entity |
| Predicate | mainMemoryCapacity |
P52984
|
FINISHED |
| Object | 4K to 32K 16-bit 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: 4K to 32K 16-bit words | Statement: [Honeywell 316 minicomputer, mainMemoryCapacity, 4K to 32K 16-bit words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMemoryCapacity Context triple: [Honeywell 316 minicomputer, mainMemoryCapacity, 4K to 32K 16-bit words]
-
A.
mainMemorySize
chosen
Indicates the relationship specifying the size or capacity of an entity's main memory.
-
B.
maxRAMOfficial
Indicates the officially specified maximum amount of RAM that is supported or allowed for an entity (such as a device or system).
-
C.
primaryMemoryType
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
D.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
E.
maxRAMUnofficial
Indicates the maximum amount of RAM that can be used or installed in an unofficial or unsupported configuration.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.