Triple
T32092453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS R2000 |
E819631
|
entity |
| Predicate | MMUImplementation |
P110870
|
FINISHED |
| Object | in coprocessor 0 |
—
|
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: in coprocessor 0 | Statement: [MIPS R2000, MMUImplementation, in coprocessor 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MMUImplementation Context triple: [MIPS R2000, MMUImplementation, in coprocessor 0]
-
A.
hasIntegratedMMU
Indicates that a system or processor includes a built-in Memory Management Unit (MMU) as part of its architecture.
-
B.
memoryManagementUnit
chosen
Indicates a relationship where a component or mechanism manages and translates memory addresses or access between different parts of a system.
-
C.
hasOnChipMMUVariantName
Indicates that an entity has a specific named variant of an on-chip Memory Management Unit (MMU) associated with it.
-
D.
memoryModel
Indicates a relationship where an entity serves as or uses a specific model or framework for representing, organizing, or managing memory.
-
E.
memoryInterface
Indicates that one entity serves as an interface or access point for interacting with, reading from, or writing to another entity’s memory.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b63edd4c819093b664b38a69d7c8 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:25 a.m.