Triple
T31593252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intze wedge |
E806156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | structural engineering concept |
C60068
|
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: structural engineering concept Context triple: [Intze wedge, instanceOf, structural engineering concept]
-
A.
engineering structure
An engineering structure is a designed and constructed system of connected components that safely resists and transmits loads to fulfill a specific functional purpose in the built environment.
-
B.
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.
-
C.
structural engineering laboratory
A structural engineering laboratory is a specialized facility where engineers and researchers experimentally test, analyze, and validate the behavior, strength, and performance of structural materials and systems under various loads and environmental conditions.
-
D.
concrete structure
A concrete structure is a physical construction made primarily from concrete, designed to bear loads and provide durable, stable support in buildings and infrastructure.
-
E.
reinforced concrete structure
A reinforced concrete structure is a construction system in which concrete is combined with embedded steel reinforcement to resist both compressive and tensile forces, providing strength, durability, and stability for buildings and infrastructure.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:29 p.m.