Triple
T11098583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSL(2,7) |
E262442
|
entity |
| Predicate | centerOfCoveringGroup |
P97223
|
FINISHED |
| Object | {±I} in SL(2,7) |
—
|
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: {±I} in SL(2,7) | Statement: [PSL(2,7), centerOfCoveringGroup, {±I} in SL(2,7)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfCoveringGroup
Context triple: [PSL(2,7), centerOfCoveringGroup, {±I} in SL(2,7)]
-
A.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0b2890819081c4efc50e995cdd |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.