Triple
T36640340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,7) |
E904566
|
entity |
| Predicate | isUniversalCentralExtensionOf |
P75140
|
FINISHED |
| Object | PSL(2,7) |
—
|
NE NERFINISHED |
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: PSL(2,7) | Statement: [SL(2,7), isUniversalCentralExtensionOf, PSL(2,7)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUniversalCentralExtensionOf Context triple: [SL(2,7), isUniversalCentralExtensionOf, PSL(2,7)]
-
A.
hasCentralExtension
chosen
Indicates that one algebraic structure is a central extension of another, meaning it fits into an exact sequence where the kernel lies in the center of the extending structure.
-
B.
isUniversalFor
Indicates that a property, rule, or condition holds true for all members of a specified set or domain without exception.
-
C.
isUniversalFor
Indicates that something applies to or is valid for all members of a given set, domain, or context without exception.
-
D.
isUniversal
Indicates that the relationship or property holds for all relevant entities or cases without exception.
-
E.
isExtensionSiteOf
Indicates that one entity serves as an additional or supplementary location, facility, or site associated with another primary entity.
- F. None of above.
Provenance (3 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.