Triple
T19285053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourier series |
E482288
|
entity |
| Predicate | usesBasisFunctions |
P135136
|
FINISHED |
| Object | sine functions |
—
|
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: sine functions | Statement: [Fourier series, usesBasisFunctions, sine functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBasisFunctions Context triple: [Fourier series, usesBasisFunctions, sine functions]
-
A.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
B.
hasCoordinateBasis
Indicates that a coordinate system or vector space is associated with a specific basis that defines its coordinates.
-
C.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
D.
hasStandardBasis
Indicates that a given vector space is equipped with or possesses its usual canonical set of basis vectors.
-
E.
hasBasinFunction
Indicates that something serves the role or performs the function of a basin, such as collecting, holding, or draining water or other substances.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0152d48190b92272d4c7caa708 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:30 p.m.