Triple
T36640630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | symmetric group S5 |
E904572
|
entity |
| Predicate | hasCompositionFactor |
P204981
|
FINISHED |
| Object | alternating group A5 |
E2192780
|
NE 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: alternating group A5 | Statement: [symmetric group S5, hasCompositionFactor, alternating group A5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompositionFactor Context triple: [symmetric group S5, hasCompositionFactor, alternating group A5]
-
A.
hasCompositionBy
Indicates that something (such as a work or piece) is composed or created by a particular composer or author.
-
B.
hasFactor
Indicates that one entity is a factor or divisor of another entity in a multiplicative relationship.
-
C.
hasCompositionType
Indicates that one entity is composed of or formed by another entity in a specific structural or material way.
-
D.
hasSecondaryComposition
Indicates that an entity possesses an additional or subordinate compositional element beyond its primary composition.
-
E.
forcesComposition
Indicates that one entity compels or determines the structural makeup or arrangement of another entity.
- F. None of above. chosen
Provenance (5 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a3814ab588190bd0d786587cb0fc2 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.