Triple
T20627439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schur algorithm |
E506855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recursive procedure |
C27361
|
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: recursive procedure Context triple: [Schur algorithm, instanceOf, recursive procedure]
-
A.
recursive function
chosen
A recursive function is a function that solves a problem by calling itself with modified arguments until reaching a base case that stops the recursion.
-
B.
recursively defined sequence
A recursively defined sequence is a sequence of numbers or objects in which each term is specified in terms of one or more preceding terms together with one or more initial values.
-
C.
recursive estimator
A recursive estimator is an algorithm that incrementally updates its estimate of an unknown quantity as new data arrive, using the previous estimate and current observation without reprocessing all past data.
-
D.
random process
A random process is a collection of random variables indexed by time or space that models the evolution of a system subject to inherent uncertainty.
-
E.
recursive DNS resolver software
Recursive DNS resolver software is a network service that receives client DNS queries and iteratively queries other DNS servers on their behalf to return the final resolved domain-to-IP mapping.
- F. None of above.
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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:42 a.m.