Triple
T27562847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legendre polynomials |
E695818
|
entity |
| Predicate | areUsedToConstruct |
P64282
|
FINISHED |
| Object | Legendre series expansions |
—
|
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: Legendre series expansions | Statement: [Legendre polynomials, areUsedToConstruct, Legendre series expansions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areUsedToConstruct Context triple: [Legendre polynomials, areUsedToConstruct, Legendre series expansions]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
C.
constructionUsed
chosen
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
ledToConstructionOf
Indicates that one entity caused, initiated, or was the primary reason for the construction or creation of another entity.
- 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.