Triple
T38538508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitehead group |
E924762
|
entity |
| Predicate | isAbelianGroup |
P152465
|
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: [Whitehead group, isAbelianGroup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAbelianGroup Context triple: [Whitehead group, isAbelianGroup, true]
-
A.
isAbelianFor
chosen
Indicates that the operation or structure associated with the given entity is commutative (i.e., forms an Abelian group) with respect to the specified context or parameters.
-
B.
hasAbelianization
Indicates that one algebraic structure is related to the abelian group obtained by quotienting it by its commutator subgroup (its abelianization).
-
C.
isPerfectGroup
Indicates that the group satisfies the definition of a perfect group, typically meaning it is equal to its own commutator subgroup (has no nontrivial abelian quotient).
-
D.
hasTrivialAbelianization
Indicates that the group’s abelianization is trivial, meaning its commutator subgroup is the whole group and it has no nontrivial abelian quotient.
-
E.
isNonAbelian
Indicates that the operation or structure in question does not satisfy commutativity, so the order of applying the operation matters.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2e7f334819094f21b6af81b5e20 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.