Triple
T28608124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R4000 |
E724106
|
entity |
| Predicate | virtualAddressSpace |
P3700
|
FINISHED |
| Object | 64-bit virtual addressing |
—
|
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: 64-bit virtual addressing | Statement: [R4000, virtualAddressSpace, 64-bit virtual addressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualAddressSpace Context triple: [R4000, virtualAddressSpace, 64-bit virtual addressing]
-
A.
addressSpaceSize
chosen
Indicates the total amount of addressable memory or identifier range allocated or available within a given address space.
-
B.
virtualizationLayer
Indicates that one entity functions as an abstraction or intermediary layer that virtualizes or emulates the underlying resources or environment of another entity.
-
C.
memoryRegion
Indicates a relationship where one entity represents or refers to a specific region or segment within a larger memory space.
-
D.
requiresVirtualMachine
Indicates that one entity depends on or must be run within a virtual machine provided by another entity in order to function or be valid.
-
E.
supportsParavirtualization
Indicates that one entity provides the capability for another entity to run in a paravirtualized environment or to use paravirtualization features.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:28 a.m.