Triple
T72942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 754 floating‑point arithmetic standard |
E1460
|
entity |
| Predicate | specifies |
P773
|
FINISHED |
| Object | single‑precision binary32 format |
—
|
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: single‑precision binary32 format | Statement: [IEEE 754 floating‑point arithmetic standard, specifies, single‑precision binary32 format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifies Context triple: [IEEE 754 floating‑point arithmetic standard, specifies, single‑precision binary32 format]
-
A.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
C.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
D.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.