Triple
T20201852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Support Division for Region V |
E493240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative support unit |
C22325
|
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: administrative support unit Context triple: [Mission Support Division for Region V, instanceOf, administrative support unit]
-
A.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
B.
aviation support unit
An aviation support unit is an organizational entity that provides maintenance, logistics, ground handling, and operational assistance to ensure the effective and safe functioning of aircraft and flight operations.
-
C.
acquisition support organization
An acquisition support organization is a specialized entity that provides expertise, resources, and services to plan, manage, and execute procurement and acquisition activities efficiently and in compliance with relevant policies and regulations.
-
D.
administrative section
chosen
An administrative section is a defined organizational unit within an institution or system responsible for managing specific administrative tasks, processes, or services.
-
E.
administrative establishment
An administrative establishment is an organization or facility responsible for managing, coordinating, and executing governmental or institutional policies, procedures, and services.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.