Triple
T6833049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cyclotomic field |
E157383
|
entity |
| Predicate | hasClassGroup |
P72932
|
FINISHED |
| Object | ideal class group depending on n |
—
|
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: ideal class group depending on n | Statement: [cyclotomic field, hasClassGroup, ideal class group depending on n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassGroup Context triple: [cyclotomic field, hasClassGroup, ideal class group depending on n]
-
A.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
-
B.
hasClass
Indicates that an entity belongs to, is categorized under, or is associated with a particular class or type.
-
C.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
D.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
E.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:18 p.m.