Triple
T36909428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutchinson–Rice–Rosengren singularity |
E912868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | asymptotic solution in fracture mechanics |
C53783
|
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: asymptotic solution in fracture mechanics Context triple: [Hutchinson–Rice–Rosengren singularity, instanceOf, asymptotic solution in fracture mechanics]
-
A.
ancient fracture network
An ancient fracture network is a preserved system of interconnected cracks and fractures in rock that formed in the geological past and now influences the rock’s mechanical behavior and fluid flow.
-
B.
nonlinear elasticity model
chosen
A nonlinear elasticity model describes how materials deform under loads when the relationship between stress and strain is nonlinear, capturing large deformations and material behaviors beyond the assumptions of linear elasticity.
-
C.
structural analysis theory
Structural analysis theory is a conceptual framework used to determine the effects of loads on physical structures and their components, ensuring safety, stability, and performance.
-
D.
solid mechanics award
A solid mechanics award is a formal recognition given to individuals or groups for outstanding contributions, research, or innovation in the field of solid mechanics.
-
E.
free boundary problem
A free boundary problem is a type of mathematical or physical problem in which the shape or position of the boundary of the domain is not known in advance and must be determined as part of the solution.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.