Triple
T22382122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U(1) |
E553299
|
entity |
| Predicate | isCommutativeLieGroup |
P19409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [U(1), isCommutativeLieGroup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommutativeLieGroup Context triple: [U(1), isCommutativeLieGroup, true]
-
A.
isCommutative
chosen
Indicates that the result of applying an operation to two entities does not depend on their order (i.e., a ∘ b = b ∘ a).
-
B.
hasLieAlgebra
Indicates that one mathematical structure is associated with, or gives rise to, a specific Lie algebra capturing its infinitesimal or tangent-level structure.
-
C.
isRealLieGroup
Indicates that the entity is a Lie group that is defined over the real numbers and satisfies the formal properties of a real Lie group.
-
D.
isSimpleAsLieGroup
Indicates that a given Lie group has no nontrivial connected normal subgroups, i.e., it is simple in the sense of Lie group theory.
-
E.
hasCommutationRelations
Indicates that there exist specific commutation relations governing how two operators or elements combine or reorder with respect to each other.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.