Triple
T5230781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Policy on Geometric Design of Highways and Streets |
E118104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering reference manual |
C2538
|
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 reference manual Context triple: [A Policy on Geometric Design of Highways and Streets, instanceOf, engineering reference manual]
-
A.
engineering journal
An engineering journal is a periodical publication that presents peer-reviewed research, technical developments, and practical applications in various fields of engineering.
-
B.
engineering standard
chosen
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 library
An engineering library is a specialized collection of technical resources, including books, journals, standards, and digital tools, that support research, education, and practice in engineering disciplines.
-
D.
engineering examination
An engineering examination is a formal assessment that evaluates a candidate’s understanding and application of engineering principles, problem-solving skills, and technical knowledge within a specific engineering discipline.
-
E.
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.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:48 p.m.