Triple
T36640414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGL(2,7) |
E904567
|
entity |
| Predicate | isTransitiveSubgroupOf |
P186111
|
FINISHED |
| Object | S_8 |
—
|
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: S_8 | Statement: [PGL(2,7), isTransitiveSubgroupOf, S_8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransitiveSubgroupOf Context triple: [PGL(2,7), isTransitiveSubgroupOf, S_8]
-
A.
isClosedSubgroupOf
Indicates that one group is a subgroup of another and is closed in the topological sense within that larger group.
-
B.
isMaximalSubgroupOf
Indicates that one group is a proper subgroup of another that is not contained in any larger proper subgroup of that group.
-
C.
isSubalgebraOf
Indicates that one algebraic structure is a subalgebra of another, meaning it is closed under the same operations and inherits the algebraic structure from the larger one.
-
D.
isSimplyTransitiveUnder
Indicates that one entity acts on another in a way that is transitive and free, so each target is reached by exactly one action of the first entity.
-
E.
isFullyInvariantSubgroup
Indicates that a subgroup remains invariant under all endomorphisms of the parent group, not just its automorphisms.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.