Triple
T6910705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hahn series |
E159923
|
entity |
| Predicate | hasExponentGroup |
P74093
|
FINISHED |
| Object | ordered abelian 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: ordered abelian group | Statement: [Hahn series, hasExponentGroup, ordered abelian group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExponentGroup Context triple: [Hahn series, hasExponentGroup, ordered abelian group]
-
A.
allowsExponentType
Indicates that one entity permits or supports the use of a specified type for an exponent in an operation or expression.
-
B.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
-
C.
hasPostgroupOperator
Indicates that one entity is associated with an operator that is applied after a primary operation or grouping has been performed on another entity.
-
D.
hasKeyGroup
Indicates that an entity is associated with a particular key group that governs or organizes its access, classification, or control.
-
E.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9c135b48190b332aedf1d52bdb7 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.