Triple
T6824006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Global Compact |
E156968
|
entity |
| Predicate | hasPrincipleCategory |
P15481
|
FINISHED |
| Object | Human Rights Principles |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Human Rights Principles | Statement: [UN Global Compact, hasPrincipleCategory, Human Rights Principles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrincipleCategory Context triple: [UN Global Compact, hasPrincipleCategory, Human Rights Principles]
-
A.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
B.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
E.
hasProgramCategory
Indicates that a program is classified under a specific category or type of program.
- F. None of above.
Provenance (3 batches)
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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d580ca448190aa6d52908ca50e39 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.