Triple
T34101294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnniac computer |
E874574
|
entity |
| Predicate | primaryMemorySize |
P52984
|
FINISHED |
| Object | 256 words (initially) |
—
|
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: 256 words (initially) | Statement: [Johnniac computer, primaryMemorySize, 256 words (initially)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMemorySize Context triple: [Johnniac computer, primaryMemorySize, 256 words (initially)]
-
A.
mainMemorySize
chosen
Indicates the relationship specifying the size or capacity of an entity's main memory.
-
B.
primaryMemoryType
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
C.
videoMemorySize
Indicates the amount of video memory associated with a graphics-related component or device.
-
D.
addressSpaceSize
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
E.
maxRAMOfficial
Indicates the officially specified maximum amount of RAM that is supported or allowed for an entity (such as a device 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.