Triple
T17094386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILO Convention No. 182 |
E414806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Human rights treaty |
C743
|
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: Human rights treaty Context triple: [ILO Convention No. 182, instanceOf, Human rights treaty]
-
A.
international human rights instrument
chosen
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.
-
B.
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.
-
C.
human rights law
Human rights law is the body of international and domestic legal norms that protects the fundamental rights and freedoms inherent to all individuals against abuse by states and other actors.
-
D.
United Nations human rights review mechanism
A United Nations human rights review mechanism is a formal, periodic process through which UN bodies assess and monitor states’ compliance with international human rights obligations, typically involving state reports, independent expert or peer review, and public recommendations for improvement.
-
E.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.