Triple
T25627364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium 120 |
E642468
|
entity |
| Predicate | supportsOnChipFPU |
P86810
|
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: [Intel Pentium 120, supportsOnChipFPU, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOnChipFPU Context triple: [Intel Pentium 120, supportsOnChipFPU, yes]
-
A.
hasVectorFloatingPointUnit
Indicates that an entity (typically a processor or core) includes a hardware unit capable of performing floating-point operations on vector (SIMD) data.
-
B.
FPU
chosen
Indicates that one entity functions as or contains a floating-point unit responsible for performing arithmetic operations on non-integer (floating-point) numbers for another entity or within a system.
-
C.
compatibleFPU
Indicates that two processing units or components can interoperate correctly and reliably with respect to floating-point operations.
-
D.
supportsNEON
Indicates that one entity provides or enables NEON (ARM Advanced SIMD) instruction set support for another entity.
-
E.
numberOfFloatingPointUnits
Indicates the quantity of floating-point processing units associated with or contained in an entity.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 21, 2026, 5:15 p.m.