Triple
T19050721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirichlet kernel |
E466248
|
entity |
| Predicate | growthNearZero |
P37890
|
FINISHED |
| Object | behaves like 2n+1 near x = 0 |
—
|
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: behaves like 2n+1 near x = 0 | Statement: [Dirichlet kernel, growthNearZero, behaves like 2n+1 near x = 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: growthNearZero Context triple: [Dirichlet kernel, growthNearZero, behaves like 2n+1 near x = 0]
-
A.
growthProperty
chosen
Indicates that one entity characterizes, constrains, or quantifies how another entity grows or changes in magnitude over some parameter (such as time, size, or input).
-
B.
growthType
Indicates the manner or pattern in which something develops or increases over time.
-
C.
growthPolicy
Indicates a rule or strategy that governs how something is allowed or expected to grow or expand over time.
-
D.
growthStatus
Indicates the current stage or condition of development or progress of an entity over time.
-
E.
growthMethod
Indicates the method or process by which something increases, develops, or expands over time.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc02597c8190b39fd2c7b7e42258 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.