Triple
T35188620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps corporate staff |
E1016056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | headquarters-level organization |
C35001
|
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: headquarters-level organization Context triple: [Marine Corps corporate staff, instanceOf, headquarters-level organization]
-
A.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
B.
bureau-level office
A bureau-level office is an organizational unit within a larger department or agency that operates at the bureau tier, managing specialized programs, policies, or services under that bureau’s authority.
-
C.
headquarters and service company
A headquarters and service company is an organizational entity that centralizes strategic management, administrative support, and shared services for multiple business units or subsidiaries.
-
D.
headquarters and service regiment
chosen
A headquarters and service regiment is a military unit that provides command, control, and essential administrative and logistical support functions for a larger formation or group of subordinate units.
-
E.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.