Triple
T26254163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | modular j-invariant |
E656674
|
entity |
| Predicate | hasPoleOrder |
P97141
|
FINISHED |
| Object | 1 at i∞ |
—
|
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: 1 at i∞ | Statement: [modular j-invariant, hasPoleOrder, 1 at i∞]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoleOrder Context triple: [modular j-invariant, hasPoleOrder, 1 at i∞]
-
A.
hasOrderOfPoleAtLatticePoints
Indicates that a function has poles of specified orders at each point of a given lattice in its domain.
-
B.
hasPoleAt
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
-
C.
orderOfPoleAt
chosen
Indicates the location or index at which a function has a pole of a specified order.
-
D.
hasHigherOrderTerm
Indicates that one entity includes or is associated with a term of higher order (e.g., higher degree, derivative, or complexity) relative to another entity or baseline.
-
E.
hasDoublePoleAt
Indicates that a function or expression has a pole of order two (a second-order singularity) at a specified point.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 26, 2026, 9:08 p.m.