Triple
T24036565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(n,ℂ) |
E595247
|
entity |
| Predicate | isDerivedSubgroupOf |
P97226
|
FINISHED |
| Object | GL(n,ℂ) |
—
|
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: GL(n,ℂ) | Statement: [SL(n,ℂ), isDerivedSubgroupOf, GL(n,ℂ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerivedSubgroupOf Context triple: [SL(n,ℂ), isDerivedSubgroupOf, GL(n,ℂ)]
-
A.
isClosedSubgroupOf
Indicates that one group is a subgroup of another and is closed in the topological sense within that larger group.
-
B.
isMaximalSubgroupOf
Indicates that one group is a proper subgroup of another that is not contained in any larger proper subgroup of that group.
-
C.
derivedSubgroup
chosen
Indicates that one group is the derived (commutator) subgroup of another, generated by all commutators of its elements.
-
D.
hasSubgroupIsomorphicTo
Indicates that one group contains a subgroup that is structurally identical (isomorphic) to another specified group.
-
E.
isCharacteristicSubgroup
Indicates that one subgroup is invariant under all automorphisms of the parent group, making it a characteristic subgroup of that group.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d43884819093e9207a99ae2a70 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.