Triple
T491597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNBIS Thesaurus |
E10201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations information system component |
C224
|
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 information system component Context triple: [UNBIS Thesaurus, instanceOf, United Nations information system component]
-
A.
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.
-
B.
information system
chosen
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
C.
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.
-
D.
UN observer state
A UN observer state is a sovereign entity that is not a full member of the United Nations but is granted the right to participate in General Assembly sessions and activities without voting rights.
-
E.
international organization
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.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.