Triple
T5425646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E(n) |
E121355
|
entity |
| Predicate | isIsometryGroupOf |
P14251
|
FINISHED |
| Object | R^n |
—
|
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: R^n | Statement: [E(n), isIsometryGroupOf, R^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIsometryGroupOf Context triple: [E(n), isIsometryGroupOf, R^n]
-
A.
hasIsometryGroup
chosen
Indicates that one entity possesses or is associated with a particular isometry group describing all distance-preserving transformations of that entity.
-
B.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
C.
hasSymmetryGroupOrder
Indicates that an entity possesses a symmetry group whose total number of distinct symmetry operations equals the given order.
-
D.
isMaximallySymmetric
Indicates that the subject exhibits the highest possible degree of symmetry allowed by the relevant structure, constraints, or context.
-
E.
isIsomorphicTo
Indicates that two structures have a one-to-one, structure-preserving correspondence between their elements, making them equivalent in form even if not identical in content.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.