Triple
T10426498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusser's law |
E245802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering law |
C27710
|
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: engineering law Context triple: [Lusser's law, instanceOf, engineering law]
-
A.
engineering licensure exam
An engineering licensure exam is a standardized professional test that assesses whether an engineer possesses the minimum competency, knowledge, and ethical understanding required to practice engineering independently and legally within a specific jurisdiction.
-
B.
engineering standard
An engineering standard is a documented set of agreed-upon technical criteria, methods, and requirements intended to ensure safety, interoperability, quality, and consistency in engineering design, production, and operation.
-
C.
engineering regulator
An engineering regulator is an entity or mechanism that establishes, enforces, and monitors technical standards, safety requirements, and compliance within engineering practices and systems.
-
D.
engineering firm
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
-
E.
civil engineer
A civil engineer is a professional who designs, constructs, and maintains infrastructure projects such as roads, bridges, buildings, and water systems to ensure safety, functionality, and sustainability.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:12 p.m.