Triple
T7338254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co1 |
E169183
|
entity |
| Predicate | hasConjugacyClasses |
P77144
|
FINISHED |
| Object | 21 |
—
|
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: 21 | Statement: [Co1, hasConjugacyClasses, 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConjugacyClasses Context triple: [Co1, hasConjugacyClasses, 21]
-
A.
conjugacyProperty
Indicates that two elements or structures are related by conjugation, sharing the same form up to an inner automorphism or similarity transformation.
-
B.
isMaximalSymmetryGroupOf
Indicates that a group represents the largest possible symmetry group for a given object or structure, such that no strictly larger symmetry group of that object exists containing it.
-
C.
hasAutomorphism
Indicates that there exists a structure-preserving bijection from an entity to itself that maintains all relevant relations and operations.
-
D.
isNonAbelian
Indicates that the operation or structure in question does not satisfy commutativity, so the order of applying the operation matters.
-
E.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
- F. None of above. chosen
Provenance (4 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.