Triple
T36876596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burger–Iozzi–Wienhard inequalities for higher rank groups |
E911358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inequality in geometry and topology |
C10054
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: inequality in geometry and topology Context triple: [Burger–Iozzi–Wienhard inequalities for higher rank groups, instanceOf, inequality in geometry and topology]
-
A.
work in geometric topology
Work in geometric topology studies the properties and structures of spaces that are preserved under continuous deformations, focusing on the interplay between geometry and topology in shapes and manifolds.
-
B.
geometric invariant
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
C.
geometric structure
A geometric structure is an abstract mathematical entity defined by sets of points and the relationships between them (such as distances, angles, or incidences) that determine its shape and spatial properties.
-
D.
tool in geometric analysis
chosen
A tool in geometric analysis is a mathematical method, concept, or construction used to study and characterize the geometric and analytic properties of spaces, shapes, and mappings.
-
E.
research program in geometry
A research program in geometry is a coordinated, long-term investigation that develops and applies geometric concepts, methods, and conjectures to systematically explore and solve interconnected mathematical problems.
- F. None of above.
Provenance (1 batch)
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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.