Triple
T26253913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E8 lattice |
E656669
|
entity |
| Predicate | discriminant |
P72928
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [E8 lattice, discriminant, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discriminant Context triple: [E8 lattice, discriminant, 1]
-
A.
discriminantOverℚ
Indicates that the discriminant of the given algebraic object is taken with respect to the field of rational numbers ℚ.
-
B.
determinant
Indicates that a particular factor or condition has a decisive influence on the outcome, state, or behavior of another entity.
-
C.
discriminatorType
Indicates the specific category or subtype used to distinguish one related entity or class from others within a shared hierarchy or grouping.
-
D.
differential
Indicates a relationship where one quantity or state is defined as the infinitesimal change or difference relative to another variable or function.
-
E.
hasDiscriminant
chosen
Indicates that a mathematical object (such as an equation, polynomial, or form) is associated with a specific discriminant value characterizing its roots or structural properties.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcc29cc81908880bd825cb12141 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:08 p.m.