Triple
T26255008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,ℤ) |
E656692
|
entity |
| Predicate | actionTypeOnUpperHalfPlane |
P160154
|
FINISHED |
| Object | fractional linear transformations |
—
|
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: fractional linear transformations | Statement: [SL(2,ℤ), actionTypeOnUpperHalfPlane, fractional linear transformations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionTypeOnUpperHalfPlane Context triple: [SL(2,ℤ), actionTypeOnUpperHalfPlane, fractional linear transformations]
-
A.
upperHalfRange
Indicates that a value, position, or element lies within the upper half of a specified range or interval.
-
B.
extendsAboveBelowPlane
Indicates that an object spans across a reference plane, with portions extending both above and below that plane.
-
C.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
D.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
E.
upperRightQuarterCharge
Indicates that one entity bears a charge or emblem positioned in the upper-right quarter of another entity’s surface or field.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:08 p.m.