Triple
T26254399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaughlin group |
E656679
|
entity |
| Predicate | hasMaximalSubgroup |
P76335
|
FINISHED |
| Object | U4(3) |
—
|
NE NERFINISHED |
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: U4(3) | Statement: [McLaughlin group, hasMaximalSubgroup, U4(3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximalSubgroup Context triple: [McLaughlin group, hasMaximalSubgroup, U4(3)]
-
A.
hasMaximalSubgroupOrder
Indicates that the subgroup in question has the greatest possible order (size) among all proper subgroups of the given group.
-
B.
isMaximalSubgroupOf
chosen
Indicates that one group is a proper subgroup of another that is not contained in any larger proper subgroup of that group.
-
C.
hasMaximalCompactSubgroupOf
Indicates that one mathematical group is the maximal compact subgroup contained within another group.
-
D.
hasNormalSubgroup
Indicates that one group is a normal subgroup of another group, meaning it is invariant under conjugation by elements of the larger group.
-
E.
isFullyInvariantSubgroup
Indicates that a subgroup remains invariant under all endomorphisms of the parent group, not just its automorphisms.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 26, 2026, 9:08 p.m.