Triple
T24806198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz quaternions |
E620663
|
entity |
| Predicate | isNoncommutative |
P26393
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hurwitz quaternions, isNoncommutative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNoncommutative Context triple: [Hurwitz quaternions, isNoncommutative, true]
-
A.
isNonassociative
Indicates that a binary operation on three or more elements yields different results when the elements are grouped in different ways, so the associative law does not hold.
-
B.
isNonAbelian
chosen
Indicates that the operation or structure in question does not satisfy commutativity, so the order of applying the operation matters.
-
C.
isCommutative
Indicates that the result of applying an operation to two entities does not depend on their order (i.e., a ∘ b = b ∘ a).
-
D.
hasCommutationRelations
Indicates that there exist specific commutation relations governing how two operators or elements combine or reorder with respect to each other.
-
E.
doesNotCommuteWith
Indicates that two operations or elements, when applied in different orders, yield different results and therefore do not commute.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:50 a.m.