Triple
T3775918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretariat-General for Administration |
E83307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence administration body |
C3213
|
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: defence administration body Context triple: [Secretariat-General for Administration, instanceOf, defence administration body]
-
A.
defence staff committee
A defence staff committee is a formal group of senior military and defence officials convened to coordinate policy, planning, and strategic decision-making for national or organizational security.
-
B.
public administration body
chosen
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.
-
C.
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.
-
D.
sports administration organization
A sports administration organization is an entity responsible for governing, regulating, and managing the operations, policies, and development of sports activities, leagues, or associations within its jurisdiction.
-
E.
rugby union governing body
A rugby union governing body is an organization responsible for overseeing, regulating, and promoting the sport of rugby union within a specific region or at an international level.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:36 p.m.