Triple
T33761184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macdonald polynomials |
E865108
|
entity |
| Predicate | parameterSpecialization |
P177832
|
FINISHED |
| Object | Schur polynomials at q = t |
—
|
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: Schur polynomials at q = t | Statement: [Macdonald polynomials, parameterSpecialization, Schur polynomials at q = t]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterSpecialization Context triple: [Macdonald polynomials, parameterSpecialization, Schur polynomials at q = t]
-
A.
exportSpecialization
Indicates a relationship where one entity specializes in exporting particular goods, services, or resources to another entity or market.
-
B.
propertyTypeSpecialization
Indicates that one property type is a more specific or specialized version of another, more general property type.
-
C.
specialCaseParameter
Indicates that a parameter is used only in specific or exceptional cases, differing from the standard or default behavior.
-
D.
branchSpecialization
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
E.
laterSpecialization
Indicates that one entity becomes a more specialized or refined version of another entity at a later point in time.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:45 a.m.