Triple
T7338602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSL(2,ℤ) |
E169191
|
entity |
| Predicate | actionFormula |
P9769
|
FINISHED |
| Object | z ↦ (az + b)/(cz + d) for matrix [[a,b],[c,d]] |
—
|
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: z ↦ (az + b)/(cz + d) for matrix [[a,b],[c,d]] | Statement: [PSL(2,ℤ), actionFormula, z ↦ (az + b)/(cz + d) for matrix [[a,b],[c,d]]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionFormula Context triple: [PSL(2,ℤ), actionFormula, z ↦ (az + b)/(cz + d) for matrix [[a,b],[c,d]]]
-
A.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
C.
actionSpace
Indicates the set of all possible actions an agent can take in a given environment or decision-making context.
-
D.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
E.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.