Triple
T18874159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNECE Regulations |
E461641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations regulation |
C41431
|
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: United Nations regulation Context triple: [UNECE Regulations, instanceOf, United Nations regulation]
-
A.
United Nations protocol
United Nations protocol is the formal set of rules, procedures, and diplomatic customs that govern conduct, precedence, ceremonies, and official interactions within and around the United Nations.
-
B.
United Nations capability
The "United Nations capability" conceptual class represents the specific powers, resources, and operational capacities the UN can deploy—such as peacekeeping, sanctions, mediation, and humanitarian assistance—to address international issues and fulfill its mandate.
-
C.
United Nations role
The "United Nations role" conceptual class represents the specific function, responsibility, or position an entity holds within the UN system, such as mediator, peacekeeper, observer, or member state.
-
D.
United Nations principles
United Nations principles are the foundational norms and values—such as sovereign equality, peaceful settlement of disputes, human rights, and international cooperation—that guide the organization’s actions and the conduct of its member states.
-
E.
United Nations report
A United Nations report is an official document produced by UN bodies that presents analysis, findings, and recommendations on international issues such as peace, development, human rights, and the environment.
- F. None of above. chosen
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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.