Triple
T34212316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dini test for convergence of Fourier series |
E877690
|
entity |
| Predicate | typicalPointNotation |
P39838
|
FINISHED |
| Object | 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: x₀ | Statement: [Dini test for convergence of Fourier series, typicalPointNotation, x₀]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPointNotation Context triple: [Dini test for convergence of Fourier series, typicalPointNotation, x₀]
-
A.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
B.
WhyteNotation
Indicates a classification relationship where a steam locomotive is described by its wheel arrangement using the Whyte notation system.
-
C.
positionInNotation
chosen
Indicates the specific place or index that an element occupies within a given ordered notation or representation.
-
D.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
E.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.