Triple
T27675290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gegenbauer polynomials |
E697761
|
entity |
| Predicate | orthogonalOn |
P76852
|
FINISHED |
| Object | [-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] | Statement: [Gegenbauer polynomials, orthogonalOn, [-1,1]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orthogonalOn Context triple: [Gegenbauer polynomials, orthogonalOn, [-1,1]]
-
A.
orthogonalityProperty
chosen
Indicates that one entity possesses the property of being orthogonal (i.e., at right angles or having zero inner product) with respect to another entity or a given reference.
-
B.
orthonormalityRelation
Indicates that a set of vectors are mutually orthogonal and each has unit length with respect to a given inner product.
-
C.
nonOrthogonality
Indicates that two vectors, directions, or subspaces are not orthogonal, meaning their inner product is nonzero and they are not mutually perpendicular.
-
D.
perpendicularTo
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
-
E.
isProjectionOnto
Indicates that one entity represents the result of projecting another entity onto a specified subspace, axis, or component.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:43 p.m.