Triple
T32092476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS R2000 |
E819631
|
entity |
| Predicate | supportsHardwareDivide |
P206178
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MIPS R2000, supportsHardwareDivide, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHardwareDivide Context triple: [MIPS R2000, supportsHardwareDivide, yes]
-
A.
supportsArbitraryPrecisionArithmetic
Indicates that the subject system or component can perform arithmetic operations with numbers of virtually unlimited size and precision, beyond fixed hardware-imposed limits.
-
B.
isDividedBy
Indicates that one quantity or entity serves as the divisor that evenly or proportionally separates another quantity or entity into parts.
-
C.
divisionResultOf
Indicates that one quantity is the numerical result obtained by dividing another quantity by a specified divisor.
-
D.
isDivisible
Indicates that one quantity can be evenly divided by another without leaving a remainder.
-
E.
FDIVBugDiscovered
Indicates that a flaw in a processor’s floating-point division implementation has been identified.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:25 a.m.