Triple
T36468915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSL(2,ℂ) |
E898490
|
entity |
| Predicate | hasQuotientMapFrom |
P186433
|
FINISHED |
| Object | SL(2,ℂ) |
—
|
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: SL(2,ℂ) | Statement: [PSL(2,ℂ), hasQuotientMapFrom, SL(2,ℂ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuotientMapFrom Context triple: [PSL(2,ℂ), hasQuotientMapFrom, SL(2,ℂ)]
-
A.
hasCoveringMapTo
Indicates that one mathematical space is related to another by a covering map, i.e., a continuous surjective map where each point in the target has a neighborhood evenly covered by disjoint homeomorphic copies in the source.
-
B.
hasCanonicalMapFrom
Indicates that there exists a standard or uniquely determined structure-preserving map from one entity to another.
-
C.
hasOrientationPreservingQuotient
Indicates that the associated quotient map preserves the original orientation structure of the space or object.
-
D.
isQuotientOf
Indicates that one quantity is the result of dividing another quantity by a specified divisor.
-
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. 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:10 p.m.