Triple
T37693629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1954 Convention relating to the Status of Stateless Persons |
E938870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | refugee and statelessness treaty |
C57682
|
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: refugee and statelessness treaty Context triple: [1954 Convention relating to the Status of Stateless Persons, instanceOf, refugee and statelessness treaty]
-
A.
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.
-
B.
refugee document
A refugee document is an official record or certificate issued by a competent authority that verifies an individual's recognized refugee status, identity, and associated rights or protections.
-
C.
refugee
A refugee is a person who has been forced to flee their home country due to persecution, conflict, violence, or a well-founded fear of such harm, and seeks safety and protection in another country.
-
D.
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.
-
E.
refugee assistance law
chosen
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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.