Triple
T28771274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS III |
E726418
|
entity |
| Predicate | pipelineModel |
P28421
|
FINISHED |
| Object | scalar pipelined RISC |
—
|
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: scalar pipelined RISC | Statement: [MIPS III, pipelineModel, scalar pipelined RISC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipelineModel Context triple: [MIPS III, pipelineModel, scalar pipelined RISC]
-
A.
pipeline
chosen
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
-
B.
pipelineTo
Indicates that data, output, or results from one process, component, or stage are directed and fed as input into another in a sequential flow.
-
C.
pipelineOperator
Indicates that one entity functions as an operator responsible for managing, controlling, or maintaining a pipeline associated with another entity.
-
D.
pipelineDestination
Indicates that one entity serves as the target or endpoint to which a pipeline directs its output or flow.
-
E.
pipelineWidth
Indicates the width or capacity of a pipeline in a process or data flow.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:15 a.m.