Triple
T24036530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GL(n,ℂ) |
E595246
|
entity |
| Predicate | quotientByCenter |
P97909
|
FINISHED |
| Object | PGL(n,ℂ) |
—
|
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: PGL(n,ℂ) | Statement: [GL(n,ℂ), quotientByCenter, PGL(n,ℂ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quotientByCenter Context triple: [GL(n,ℂ), quotientByCenter, PGL(n,ℂ)]
-
A.
quotientedBy
chosen
Indicates that one structure or set is formed from another by identifying elements according to an equivalence relation or partition, yielding a quotient.
-
B.
isQuotientOf
Indicates that one quantity is the result of dividing another quantity by a specified divisor.
-
C.
quotientIs
Indicates that one entity is the result of dividing another entity by a specified divisor (i.e., it represents the quotient in a division relationship).
-
D.
hasTrivialCenter
Indicates that the group’s center consists only of the identity element, meaning it has no nontrivial elements that commute with all others.
-
E.
isSubquotientOf
Indicates that one object can be obtained from another by first taking a subobject and then forming a quotient of that subobject.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d43884819093e9207a99ae2a70 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.