Triple
T26253925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E8 lattice |
E656669
|
entity |
| Predicate | hasRootsOfNorm |
P168913
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [E8 lattice, hasRootsOfNorm, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootsOfNorm Context triple: [E8 lattice, hasRootsOfNorm, 2]
-
A.
containsRootsOfUnity
Indicates that one mathematical object includes all elements that are roots of unity within a specified context or structure.
-
B.
hasMinimalPolynomialOverQ
Indicates that one element is the minimal polynomial over the rational numbers ℚ of another element, i.e., the monic irreducible polynomial in ℚ[x] for which that element is a root.
-
C.
hasRootSystem
Indicates that one entity possesses or is characterized by a particular type of root system.
-
D.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
-
E.
hasAssociatedPolynomial
Indicates that one entity is linked to another entity that serves as its associated polynomial, typically representing or characterizing some of its properties or behavior.
- 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_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 26, 2026, 9:08 p.m.