Triple
T14152841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UltraSPARC T1 |
E350729
|
entity |
| Predicate | floatingPointUnits |
P91927
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [UltraSPARC T1, floatingPointUnits, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floatingPointUnits Context triple: [UltraSPARC T1, floatingPointUnits, 1]
-
A.
numberOfFloatingPointUnits
chosen
Indicates the quantity of floating-point processing units associated with or contained in an entity.
-
B.
floatingPointRegisterCount
Indicates the number of floating-point registers associated with an entity (such as a processor or execution context).
-
C.
FPU
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.
-
D.
floatingPointPerformance
Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
-
E.
supportsFloatingPoint
Indicates that an entity is capable of handling or operating with floating-point (non-integer) numeric values.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6133754881908e1e97db71772deb |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.