Triple
T878047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO International Staff |
E18966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international organization staff |
C2192
|
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 organization staff Context triple: [NATO International Staff, instanceOf, international organization staff]
-
A.
international organization secretariat
An international organization secretariat is the permanent administrative body that supports the organization’s operations by providing coordination, technical expertise, and day-to-day management of its programs and decision-making processes.
-
B.
international civil servant
chosen
An international civil servant is a non-partisan professional employed by an intergovernmental organization to implement its mandates, support member states, and uphold international norms and agreements.
-
C.
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.
-
D.
international public office
An international public office is an organizational unit within an intergovernmental or supranational body that performs administrative, regulatory, or policy functions across national boundaries in the public interest.
-
E.
international office
An international office is an organizational unit that manages and supports an institution’s global activities, partnerships, and services for international stakeholders.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.