Triple
T31023883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frobenius conjugacy class |
E790517
|
entity |
| Predicate | hasDefiningGroup |
P196048
|
FINISHED |
| Object | Galois group |
—
|
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: Galois group | Statement: [Frobenius conjugacy class, hasDefiningGroup, Galois group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefiningGroup Context triple: [Frobenius conjugacy class, hasDefiningGroup, Galois group]
-
A.
hasDefinition
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
B.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
C.
hasObjectGroup
Indicates that an entity is associated with a specific group or collection of objects treated as a single unit.
-
D.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
-
E.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69fe031af3248190816da6829aef7bab |
completed | May 8, 2026, 3:36 p.m. |
Created at: April 29, 2026, 8:58 p.m.