Triple
T7150184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galilean group |
E166672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kinematical group |
C20392
|
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: kinematical group Context triple: [Galilean group, instanceOf, kinematical group]
-
A.
spacetime symmetry group
chosen
A spacetime symmetry group is the mathematical group of transformations (such as translations, rotations, and boosts) that leave the physical laws or geometric structure of spacetime invariant.
-
B.
representation of the Lorentz group
A representation of the Lorentz group is a mathematical structure (typically a vector space with linear operators) on which the Lorentz transformations act in a way that preserves the group operations, allowing physical fields or states to transform consistently under changes of inertial reference frames.
-
C.
pseudogroup
A pseudogroup is a collection of local homeomorphisms (or diffeomorphisms) on a topological space that is closed under composition, inversion, restriction to open subsets, and gluing of compatible local maps, generalizing the notion of a group action to local symmetries.
-
D.
non-compact Lie group
A non-compact Lie group is a Lie group whose underlying topological space is not compact, meaning it is a smooth group manifold that is unbounded or not closed in the sense of compactness.
-
E.
topological group
A topological group is a group equipped with a topology such that the group operation and inversion are continuous maps with respect to that topology.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.