Triple
T7303372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 80286 |
E167913
|
entity |
| Predicate | maxPhysicalAddressSpace |
P3700
|
FINISHED |
| Object | 16 MB |
—
|
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: 16 MB | Statement: [Intel 80286, maxPhysicalAddressSpace, 16 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxPhysicalAddressSpace Context triple: [Intel 80286, maxPhysicalAddressSpace, 16 MB]
-
A.
addressSpaceSize
chosen
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
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.
maxRAMUnofficial
Indicates the maximum amount of RAM that can be used or installed in an unofficial or unsupported configuration.
-
D.
mainMemorySize
Indicates the relationship specifying the size or capacity of an entity's main memory.
-
E.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.