Triple
T30354920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi authorities (heritage context) |
E772117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental body collective |
C172
|
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: governmental body collective Context triple: [Saudi authorities (heritage context), instanceOf, governmental body collective]
-
A.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
B.
governing body
chosen
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.
-
C.
collective political entity
A collective political entity is an organized group of individuals or communities that exercises or claims shared authority, representation, and decision-making power within a defined political framework.
-
D.
administrative body collection
An administrative body collection is an organized grouping of official entities or agencies responsible for managing, regulating, or overseeing specific governmental or institutional functions.
-
E.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:56 p.m.