Triple
T51097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security and Safety Service |
E1002
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations body |
C281
|
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 body Context triple: [United Nations Security and Safety Service, instanceOf, United Nations body]
-
A.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
B.
international organization
chosen
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
C.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
international economic organization
An international economic organization is an institution formed by multiple countries to coordinate and regulate economic policies, trade, finance, and development 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.