Triple
T847106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Labour Recommendations |
E18300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international labour standard |
C758
|
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: international labour standard Context triple: [International Labour Recommendations, instanceOf, international labour standard]
-
A.
international standard
An international standard is an agreed-upon set of rules, guidelines, or specifications established by recognized global bodies to ensure compatibility, safety, and quality across countries and industries.
-
B.
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.
-
C.
labor law
chosen
Labor law is the body of rules and principles governing the rights, duties, and relationships between employers, employees, and labor organizations in the workplace.
-
D.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
-
E.
international legal regime
An international legal regime is a structured set of principles, norms, rules, and decision-making procedures agreed upon by states and other actors to govern behavior and cooperation in a specific issue-area of international relations.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.