Triple
T17020459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littlewood–Paley theory |
E412933
|
entity |
| Predicate | mainTool |
P28572
|
FINISHED |
| Object | frequency decomposition of 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: frequency decomposition of functions | Statement: [Littlewood–Paley theory, mainTool, frequency decomposition of functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTool Context triple: [Littlewood–Paley theory, mainTool, frequency decomposition of functions]
-
A.
typicalTools
Indicates that the related tools are commonly or characteristically used to perform the associated activity, task, or function.
-
B.
toolIn
chosen
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
C.
officialToolFor
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
-
D.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
E.
mainFunctions
Indicates that the subject serves as the primary or central functional component or role for the object.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d482c3a0819099e6ea4acb0a08ee |
completed | April 18, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.