Triple
T19285090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourier series |
E482288
|
entity |
| Predicate | basisProperty |
P135137
|
FINISHED |
| Object | orthogonality of sines and cosines |
—
|
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: orthogonality of sines and cosines | Statement: [Fourier series, basisProperty, orthogonality of sines and cosines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisProperty Context triple: [Fourier series, basisProperty, orthogonality of sines and cosines]
-
A.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
B.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
C.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
D.
estateCharacteristic
Indicates that an estate possesses a particular attribute, quality, or defining feature.
-
E.
propertyForm
Indicates the specific form, type, or configuration that a property takes within a given context or system.
- 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.