Triple
T33761148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack polynomials |
E865107
|
entity |
| Predicate | limitOf |
P9149
|
FINISHED |
| Object | Macdonald polynomials as q → 1, t = q^α |
—
|
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: Macdonald polynomials as q → 1, t = q^α | Statement: [Jack polynomials, limitOf, Macdonald polynomials as q → 1, t = q^α]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitOf Context triple: [Jack polynomials, limitOf, Macdonald polynomials as q → 1, t = q^α]
-
A.
isLimitOf
chosen
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
C.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
D.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
E.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.