Triple
T27562836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legendre polynomials |
E695818
|
entity |
| Predicate | haveDegree |
P163286
|
FINISHED |
| Object | n for P_n(x) |
—
|
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: n for P_n(x) | Statement: [Legendre polynomials, haveDegree, n for P_n(x)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveDegree Context triple: [Legendre polynomials, haveDegree, n for P_n(x)]
-
A.
hasDegree
Indicates that an entity possesses or has been awarded a specific academic or professional degree.
-
B.
hasHighestDegree
Indicates that one entity possesses the highest academic degree attained by another entity.
-
C.
hasHigherDegree
Indicates that one entity possesses an academic degree that is of a higher level than the academic degree held by another entity.
-
D.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
-
E.
hasHighestDegreeTitle
Indicates that one entity holds the most advanced or highest-ranking academic degree title associated with another entity.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 1:40 p.m.