Triple
T26254421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thompson group Th |
E656680
|
entity |
| Predicate | isSporadicGroupNumber |
P37553
|
FINISHED |
| Object | 22 |
—
|
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: 22 | Statement: [Thompson group Th, isSporadicGroupNumber, 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSporadicGroupNumber Context triple: [Thompson group Th, isSporadicGroupNumber, 22]
-
A.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
B.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
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.
identifiesGroup
Indicates that one entity serves to recognize, label, or distinguish another entity as belonging to a particular group or category.
-
E.
isSpurOf
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 9:08 p.m.