Triple
T25741649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMA3 |
E648231
|
entity |
| Predicate | roundingBehavior |
P159805
|
FINISHED |
| Object | single rounding for multiply-add sequence |
—
|
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 rounding for multiply-add sequence | Statement: [FMA3, roundingBehavior, single rounding for multiply-add sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundingBehavior Context triple: [FMA3, roundingBehavior, single rounding for multiply-add sequence]
-
A.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
B.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
C.
rounded
Indicates that one entity has been made or become rounder or more curved in shape, often by smoothing or adjusting its edges or values.
-
D.
roundFormat
Indicates the specific structure, rules, or style in which a particular round of an event, game, or process is conducted.
-
E.
roundAdvancedTo
Indicates advancing an entity to a subsequent round or stage that is beyond the current or basic progression level.
- F. None of above. chosen
Provenance (4 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1b3010819098da2e7d46dfc326 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 3:45 a.m.