Triple
T26254239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griess algebra |
E656676
|
entity |
| Predicate | hasInvariantBilinearForm |
P181632
|
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: [Griess algebra, hasInvariantBilinearForm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInvariantBilinearForm Context triple: [Griess algebra, hasInvariantBilinearForm, yes]
-
A.
bracketIsBilinear
Indicates that the bracket operation is linear in each of its two arguments when the other is held fixed.
-
B.
associatedQuadraticFormProperty
Indicates that a quadratic form is linked to, or characterized by, a specific property or attribute related to its structure or behavior.
-
C.
bracketIsZBilinear
Indicates that the bracket operation is bilinear in both arguments over the base ring or field Z, i.e., it is linear in each argument when the other is held fixed.
-
D.
hasJordanForm
Indicates that one mathematical object (typically a matrix or linear operator) possesses a specific Jordan normal form associated with it.
-
E.
hasDualBasis
Indicates that one mathematical structure serves as the dual basis corresponding to another basis, typically in a dual vector space.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 26, 2026, 9:08 p.m.