Triple
T27562856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legendre polynomials |
E695818
|
entity |
| Predicate | haveValueAtMinusOne |
P43786
|
FINISHED |
| Object | P_n(-1) = (-1)^n |
—
|
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: P_n(-1) = (-1)^n | Statement: [Legendre polynomials, haveValueAtMinusOne, P_n(-1) = (-1)^n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveValueAtMinusOne Context triple: [Legendre polynomials, haveValueAtMinusOne, P_n(-1) = (-1)^n]
-
A.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
B.
hasZeroPosition
Indicates that an entity occupies or is assigned to the reference (zero) position within a defined coordinate system or ordered structure.
-
C.
valueAt
chosen
Indicates that one entity specifies the value or content associated with another entity at a particular point, position, or context.
-
D.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
E.
offsetValue
Indicates the numerical amount by which one value, position, or parameter is shifted or adjusted relative to a reference 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fbbc4408190b9afd456a429f61b |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:40 p.m.