Triple
T37167716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Civil Registry Database (Colombia) |
E920833
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil registry database |
C30007
|
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: civil registry database Context triple: [National Civil Registry Database (Colombia), instanceOf, civil registry database]
-
A.
population registry
chosen
A population registry is a centralized system that records and maintains up-to-date information about individuals residing within a defined jurisdiction, such as their identity, demographic details, and legal status.
-
B.
population registration process
The population registration process is the systematic procedure by which authorities collect, verify, and maintain up-to-date records of individuals residing within a defined jurisdiction for legal, administrative, and statistical purposes.
-
C.
vital record
A vital record is an official government document that records key life events of individuals, such as births, deaths, marriages, and divorces, for legal and statistical purposes.
-
D.
population registration law
A population registration law is a legal framework that mandates the systematic recording, maintenance, and regulation of personal data about residents or citizens within a jurisdiction for identification, administrative, and statistical purposes.
-
E.
basisregistratie
A basisregistratie is an authoritative, government-maintained foundational registry that records essential, standardized data about key entities (such as persons, addresses, or buildings) for consistent use across public services.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.