Triple
T16088551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Protocol Office of Saint Vincent and the Grenadines |
E390296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state protocol office |
C10322
|
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: state protocol office Context triple: [State Protocol Office of Saint Vincent and the Grenadines, instanceOf, state protocol office]
-
A.
state protocol
chosen
A state protocol is a formal set of rules and procedures that governs how a state’s institutions, officials, and symbols interact internally and with other states to ensure order, recognition, and continuity.
-
B.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
C.
state council office
The state council office is an administrative body that supports the state council by coordinating policy implementation, managing governmental affairs, and providing organizational and logistical services.
-
D.
state civil service
State civil service is the organized body of government employees at the state level who are hired and managed under merit-based rules to administer public programs and implement state policies.
-
E.
provincial government agency
A provincial government agency is a public-sector organization established by a provincial authority to implement policies, deliver services, and regulate activities within its jurisdiction.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 4:59 a.m.