Triple
T18719082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters and Service Company, 26th Marines |
E457720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | headquarters and service company |
C40681
|
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 and service company Context triple: [Headquarters and Service Company, 26th Marines, instanceOf, headquarters and service company]
-
A.
headquarters and service regiment
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.
-
B.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
C.
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.
-
D.
shared service centre
A shared service centre is a centralized organizational unit that consolidates and delivers common support functions (such as finance, HR, or IT) to multiple business units to improve efficiency, standardization, and cost-effectiveness.
-
E.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
- F. None of above. chosen
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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.