Triple
T15999430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitachi SH-4 |
E388057
|
entity |
| Predicate | hasFloatingPointUnit |
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: [Hitachi SH-4, hasFloatingPointUnit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloatingPointUnit Context triple: [Hitachi SH-4, hasFloatingPointUnit, yes]
-
A.
numberOfFloatingPointUnits
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
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.
-
D.
supportsFloatingPoint
Indicates that an entity is capable of handling or operating with floating-point (non-integer) numeric values.
-
E.
floatingPointUnitSharing
Indicates that two or more processing units share access to a common floating-point execution resource rather than each having a dedicated one.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.