Triple
T36640397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGL(2,7) |
E904567
|
entity |
| Predicate | hasOrderOfSylow7Subgroup |
P97224
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [PGL(2,7), hasOrderOfSylow7Subgroup, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderOfSylow7Subgroup Context triple: [PGL(2,7), hasOrderOfSylow7Subgroup, 7]
-
A.
hasSylowSubgroupOrder
chosen
Indicates that a group possesses a Sylow subgroup whose order is the specified value.
-
B.
hasSylowSubgroupForPrime
Indicates that a group possesses a Sylow subgroup corresponding to the given prime.
-
C.
hasNonAbelianSylow2Subgroups
Indicates that the Sylow 2-subgroups of a given group are non-abelian, i.e., their group operation is not commutative.
-
D.
hasElementOfOrder
Indicates that a structure (such as a group) contains an element whose order (the smallest positive integer n such that the element raised to the n-th power is the identity) equals a specified value.
-
E.
hasPrimeDivisorsOfOrder
Indicates that one entity possesses prime divisors whose multiplicities (orders in its factorization) satisfy a specified relational condition with respect to another entity.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:11 p.m.