Triple
T33513048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin system |
E858297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | asylum responsibility allocation mechanism |
C27918
|
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: asylum responsibility allocation mechanism Context triple: [Dublin system, instanceOf, asylum responsibility allocation mechanism]
-
A.
asylum support mechanism
An asylum support mechanism is a structured system of legal, social, and material assistance designed to help individuals seeking refuge navigate asylum procedures and meet their basic needs during the process.
-
B.
asylum system
chosen
The asylum system is the set of laws, institutions, and procedures through which individuals fleeing persecution or serious harm seek and may obtain international protection in a host country.
-
C.
refugee authority
A refugee authority is a governmental or designated body responsible for assessing asylum claims, granting refugee status, and coordinating protection and support services for displaced persons.
-
D.
refugee protection framework
A refugee protection framework is a structured set of laws, policies, and procedures designed to ensure the safety, rights, and durable solutions for individuals fleeing persecution, conflict, or serious human rights violations.
-
E.
refugee assistance law
Refugee assistance law is a legal framework that governs the protection, rights, services, and support provided to individuals who have fled their home countries due to persecution, conflict, or violence.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.