Triple
T6833643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagrange’s planetary equations |
E157396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | perturbation theory tool |
C14066
|
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: perturbation theory tool Context triple: [Lagrange’s planetary equations, instanceOf, perturbation theory tool]
-
A.
perturbative method in quantum mechanics
A perturbative method in quantum mechanics is an approximate technique for solving complex quantum systems by expanding physical quantities in a power series around a solvable reference problem, treating the difference as a small correction.
-
B.
computational tool
A computational tool is a software or hardware resource designed to perform, automate, or assist with data processing, analysis, or problem-solving tasks.
-
C.
tool in general relativity
chosen
A tool in general relativity is any mathematical, conceptual, or computational method used to formulate, analyze, or solve problems involving the curvature of spacetime and its interaction with matter and energy.
-
D.
tool in signal processing
A tool in signal processing is a conceptual or physical mechanism—such as an algorithm, filter, transform, or software module—used to analyze, modify, or extract information from signals.
-
E.
spectroscopic approximation
A spectroscopic approximation is a simplified theoretical or computational model used to estimate spectroscopic properties (such as energy levels, transition frequencies, or intensities) by neglecting or approximating certain physical effects to make calculations tractable.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:18 p.m.