Triple
T28501793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Board staff |
E721253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval administrative staff |
C45219
|
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: naval administrative staff Context triple: [Royal Navy Board staff, instanceOf, naval administrative staff]
-
A.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
B.
naval office
A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
-
C.
naval officer
A naval officer is a commissioned leader in a navy responsible for commanding personnel and vessels, making strategic and tactical decisions, and ensuring the effective operation and readiness of maritime forces.
-
D.
staff corps of the United States Navy
chosen
The staff corps of the United States Navy are specialized officer communities—such as medical, supply, civil engineering, legal, and chaplain corps—that provide professional support services essential to the Navy’s operations and readiness.
-
E.
naval organization
A naval organization is a structured entity responsible for managing, operating, and supporting a nation's maritime military forces, including ships, personnel, and related infrastructure.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:07 a.m.