Triple
T27706549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pass Laws in South Africa |
E698572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal passport system |
C24643
|
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: internal passport system Context triple: [Pass Laws in South Africa, instanceOf, internal passport system]
-
A.
passport authority
An organization or government agency responsible for issuing, renewing, and regulating passports and related travel documents for citizens.
-
B.
passport union
A passport union is an agreement between two or more jurisdictions that allows citizens to travel, reside, and often work across member states using a shared or mutually recognized passport system with minimal border controls.
-
C.
labor migration system
A labor migration system is the structured set of policies, institutions, processes, and social networks that govern and shape the movement of workers across regions or countries, including their recruitment, rights, conditions, and integration.
-
D.
official record system
An official record system is a structured, authoritative repository and management framework for creating, storing, tracking, and preserving formal documents and data that serve as the definitive source of truth for an organization or jurisdiction.
-
E.
population registration process
chosen
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.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3 p.m.