Triple
T27675248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chebyshev polynomials of the first kind |
E697760
|
entity |
| Predicate | T_2(x) |
P62306
|
FINISHED |
| Object | 2x^2 - 1 |
—
|
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: 2x^2 - 1 | Statement: [Chebyshev polynomials of the first kind, T_2(x), 2x^2 - 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: T_2(x) Context triple: [Chebyshev polynomials of the first kind, T_2(x), 2x^2 - 1]
-
A.
a(2)
Indicates that one entity is associated with or characterized by the property, role, or relation labeled "a(2)" in the given context.
-
B.
secondTermCalled
Indicates that the second term in a pair or relation is referred to or named by a particular label or designation.
-
C.
secondElement
chosen
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
D.
γ_2
Indicates a secondary or alternative form of the γ relationship between entities, often representing a variant, refinement, or subordinate instance of the primary γ relation.
-
E.
secondSyllableTone
Indicates that the relationship specifies the tonal value or pitch pattern of the second syllable in a word or utterance.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63532e35881909bfe0a8a315e2efe |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:43 p.m.