Triple
T25956920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directorate of Intelligence |
E645431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | analytic branch |
C50154
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: analytic branch Context triple: [Directorate of Intelligence, instanceOf, analytic branch]
-
A.
analytic function
An analytic function is a complex-valued function that is locally given by a convergent power series, meaning it is differentiable at every point in its domain and in a neighborhood around each point.
-
B.
analytic functional
An analytic functional is a continuous linear functional defined on a space of analytic functions, often represented via integration against a complex measure or distribution.
-
C.
operation on analytic functions
An operation on analytic functions is a rule or transformation that takes one or more analytic (holomorphic) functions as input and produces another function, typically preserving analyticity within a given domain.
-
D.
maximal analytic extension
A maximal analytic extension is the largest possible extension of a given spacetime (or manifold with metric) in which the metric and its geodesics can be continued analytically without introducing further removable boundaries or singularities.
-
E.
pathological function in analysis
A pathological function in analysis is a deliberately constructed example that defies typical intuitions—often satisfying formal definitions while exhibiting extreme or counterintuitive behavior, such as being continuous everywhere but differentiable nowhere.
- F. None of above. chosen
Provenance (1 batch)
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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:46 a.m.