Triple
T10287521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Compact on Refugees |
E241270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non‑binding international instrument |
C4537
|
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: non‑binding international instrument Context triple: [Global Compact on Refugees, instanceOf, non‑binding international instrument]
-
A.
legally binding international instrument
A legally binding international instrument is a formal agreement between states or international actors that creates enforceable rights and obligations under international law.
-
B.
soft law instrument
chosen
A soft law instrument is a non-binding agreement, guideline, or standard that influences behavior and shapes legal expectations without having formal, enforceable legal force.
-
C.
international normative instrument
An international normative instrument is a formal document, such as a treaty, convention, declaration, or guideline, adopted by states or international organizations to establish shared standards, principles, or rules of conduct in the international arena.
-
D.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
E.
international human rights instrument
An international human rights instrument is a formal, legally or politically binding document adopted by states or international organizations that defines, codifies, and promotes the protection of fundamental human rights and freedoms across national borders.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:40 a.m.