Triple
T36468741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möbius transformation |
E898486
|
entity |
| Predicate | associatedMatrixGroup |
P114713
|
FINISHED |
| Object | SL(2,ℂ) |
E174597
|
NE 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: [Möbius transformation, associatedMatrixGroup, SL(2,ℂ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMatrixGroup Context triple: [Möbius transformation, associatedMatrixGroup, SL(2,ℂ)]
-
A.
associatedMatrixPrefix
Indicates that one entity serves as a matrix-related prefix or leading component that is systematically associated with another entity.
-
B.
associatedModalityGroup
Indicates a relationship where something is linked to, or grouped under, a specific modality category or set of modalities.
-
C.
refersToGroupAssociatedWith
chosen
Indicates that one entity makes reference to a group that is associated or linked with another specified entity.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
- F. None of above.
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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfd308d08190abcc9238d2060a78 |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.