Triple
T32013513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KA10 |
E817470
|
entity |
| Predicate | floatingPointFormat |
P6941
|
FINISHED |
| Object | 36-bit floating point |
—
|
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: 36-bit floating point | Statement: [KA10, floatingPointFormat, 36-bit floating point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floatingPointFormat Context triple: [KA10, floatingPointFormat, 36-bit floating point]
-
A.
roundFormat
Indicates the specific structure, rules, or style in which a particular round of an event, game, or process is conducted.
-
B.
floatingPointPerformance
Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
-
C.
floatType
chosen
Indicates that an entity has a specific floating-point data type or is categorized as a floating-point numeric value.
-
D.
supportsFloatingPoint
Indicates that an entity is capable of handling or operating with floating-point (non-integer) numeric values.
-
E.
floatingPointPipelines
Indicates a relationship where one or more entities are involved in, implement, or are associated with pipelines that process floating-point numerical operations.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b43932788190bff57095264a917d |
completed | May 3, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:15 a.m.