Triple
T26254916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T : z ↦ z + 1 |
E656690
|
entity |
| Predicate | generatesSubgroup |
P160547
|
FINISHED |
| Object | ⟨T⟩ ≅ ℤ |
—
|
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: ⟨T⟩ ≅ ℤ | Statement: [T : z ↦ z + 1, generatesSubgroup, ⟨T⟩ ≅ ℤ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatesSubgroup Context triple: [T : z ↦ z + 1, generatesSubgroup, ⟨T⟩ ≅ ℤ]
-
A.
usesSubgroup
Indicates that one entity employs, incorporates, or operates through a specific subgroup of another entity or system.
-
B.
subgroupCategory
Indicates that one category functions as a more specific subgroup within the scope of another, broader category.
-
C.
revealedAsSubgroupOf
Indicates that one group has been newly identified or exposed as being a subgroup or subset of another group.
-
D.
derivedSubgroup
Indicates that one group is the derived (commutator) subgroup of another, generated by all commutators of its elements.
-
E.
hasSpecialSubgroup
Indicates that an entity includes or is associated with a particular subgroup that has distinctive or exceptional properties compared to its other subgroups.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 9:08 p.m.