Triple
T27675260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chebyshev polynomials of the first kind |
E697760
|
entity |
| Predicate | rangeOnInterval |
P40693
|
FINISHED |
| Object | [-1,1] on [-1,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: [-1,1] on [-1,1] | Statement: [Chebyshev polynomials of the first kind, rangeOnInterval, [-1,1] on [-1,1]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeOnInterval Context triple: [Chebyshev polynomials of the first kind, rangeOnInterval, [-1,1] on [-1,1]]
-
A.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
D.
rangeSection
chosen
Indicates a specific contiguous subset or span within a larger ordered range.
-
E.
rangeRestrictedTo
Indicates that the possible values or targets of a relation are constrained to lie within a specified set or type.
- 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.