Triple
T20719786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy administration (historical) |
E509280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval administration system |
C4787
|
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 administration system Context triple: [Royal Navy administration (historical), instanceOf, naval administration system]
-
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
chosen
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 arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
-
D.
naval defense system
A naval defense system is an integrated network of sensors, weapons, platforms, and command-and-control components designed to detect, deter, and neutralize maritime threats to ships, fleets, and coastal assets.
-
E.
naval shore establishment
A naval shore establishment is a land-based facility that supports a navy’s operations, administration, training, logistics, and maintenance away from seagoing vessels.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:26 p.m.