Triple
T3966866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Motor Vehicle Administration |
E92237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | motor vehicle administration |
C9123
|
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: motor vehicle administration Context triple: [Maryland Motor Vehicle Administration, instanceOf, motor vehicle administration]
-
A.
division of a state transportation department
chosen
A division of a state transportation department is an organizational unit responsible for managing specific functions—such as planning, construction, maintenance, or safety—within the broader mission of developing and operating the state's transportation system.
-
B.
transportation safety agency
A transportation safety agency is an organization responsible for regulating, monitoring, and enforcing safety standards across transportation systems to prevent accidents and protect the public.
-
C.
state police agency
A state police agency is a government law enforcement organization with statewide jurisdiction responsible for enforcing laws, maintaining public order, and supporting local agencies across the entire state.
-
D.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
E.
highway patrol
A highway patrol is a specialized law enforcement unit responsible for monitoring and enforcing traffic laws, ensuring road safety, and responding to incidents on highways and major roadways.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:32 p.m.