Triple
T28771271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS III |
E726418
|
entity |
| Predicate | coprocessorModel |
P165569
|
FINISHED |
| Object | CP0 system control coprocessor |
—
|
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: CP0 system control coprocessor | Statement: [MIPS III, coprocessorModel, CP0 system control coprocessor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coprocessorModel Context triple: [MIPS III, coprocessorModel, CP0 system control coprocessor]
-
A.
coprocessorInterface
Indicates a relationship where one component provides or uses an interface to coordinate operations with a coprocessor.
-
B.
coprocessorNumber
Indicates the identifying number assigned to a specific coprocessor associated with a processor or system.
-
C.
separateCoprocessorModels
Indicates that distinct models or representations are maintained for coprocessors, rather than sharing or combining them with other processing components.
-
D.
numericCoprocessorSupport
Indicates that a system or processor includes and can utilize a dedicated numeric coprocessor for performing arithmetic or mathematical operations.
-
E.
cpuModel
Indicates the specific processor model associated with a given computing device or system.
- F. None of above. chosen
Provenance (4 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:15 a.m.