Triple
T36871428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gromov hyperbolic group |
E911231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geometric group theory concept |
C30619
|
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: geometric group theory concept Context triple: [Gromov hyperbolic group, instanceOf, geometric group theory concept]
-
A.
group theory concept
chosen
A group theory concept is an abstract mathematical idea that studies sets equipped with a single associative operation satisfying identity and inverse properties, used to analyze symmetry and structure across diverse mathematical systems.
-
B.
concept in finite group theory
A class in finite group theory is a subset of group elements that are equivalent under conjugation, meaning each element can be transformed into any other in the subset by an inner automorphism of the group.
-
C.
concept in group theory
A class in group theory is a subset of group elements that are equivalent under conjugation, meaning each element can be written as g⁻¹ag for some fixed a and varying g in the group.
-
D.
finitely generated group
A finitely generated group is a group for which there exists a finite set of elements such that every element of the group can be expressed as a finite product of these elements and their inverses.
-
E.
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.
- 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.