Triple
T11919034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitting decomposition |
E283605
|
entity |
| Predicate | usesSubgroup |
P102351
|
FINISHED |
| Object | largest nilpotent normal subgroup |
—
|
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: largest nilpotent normal subgroup | Statement: [Fitting decomposition, usesSubgroup, largest nilpotent normal subgroup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubgroup Context triple: [Fitting decomposition, usesSubgroup, largest nilpotent normal subgroup]
-
A.
subgroupCategory
Indicates that one category functions as a more specific subgroup within the scope of another, broader category.
-
B.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
C.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
D.
derivedSubgroup
Indicates that one group is the derived (commutator) subgroup of another, generated by all commutators of its elements.
-
E.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.