Triple
T25686342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Register of Motor Vehicles (Vahan) |
E644076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | centralized digital database |
C49802
|
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: centralized digital database Context triple: [National Register of Motor Vehicles (Vahan), instanceOf, centralized digital database]
-
A.
national electronic database
chosen
A national electronic database is a centralized digital system that securely stores, manages, and provides authorized access to large-scale data relevant to a country’s population, institutions, or services.
-
B.
database
A database is an organized collection of structured or unstructured data stored and managed in a way that enables efficient retrieval, modification, and administration.
-
C.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
D.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
E.
card-based database program
A card-based database program is a software application that organizes, stores, and manages information as individual "cards" or records, each containing related fields of data that can be easily viewed, edited, sorted, and searched.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:09 p.m.