Triple
T244254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz transformation |
E5001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | concept in special relativity |
C937
|
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: concept in special relativity Context triple: [Lorentz transformation, instanceOf, concept in special relativity]
-
A.
concept
chosen
A concept is an abstract idea or mental representation that groups together related objects, events, or qualities based on shared characteristics.
-
B.
momentum conservation paradox
A momentum conservation paradox is an apparent contradiction in a physical scenario where the total momentum seems not to be conserved, typically arising from incomplete analysis, neglected interactions, or misapplied reference frames.
-
C.
solution in general relativity
A solution in general relativity is a specific spacetime metric (and accompanying matter fields, if any) that satisfies Einstein’s field equations for a given physical configuration or set of conditions.
-
D.
technology concept
A technology concept is an abstract idea or blueprint that outlines how a particular technological solution, system, or innovation could function to address a specific need or problem.
-
E.
operational concept
An operational concept is a high-level description of how a system, organization, or capability is intended to function in practice to achieve its objectives within a specific context.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.