Triple
T37522575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty orders and draughts of 1719 |
E932818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Admiralty document |
C65823
|
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: British Admiralty document Context triple: [Admiralty orders and draughts of 1719, instanceOf, British Admiralty document]
-
A.
International Hydrographic Organization publication
An International Hydrographic Organization publication is an official document issued by the IHO that provides standardized guidance, specifications, or information related to hydrography, nautical charting, and maritime navigation.
-
B.
Royal Navy organization
A Royal Navy organization is a structured entity within the United Kingdom’s naval service responsible for planning, directing, and supporting maritime operations, personnel, and resources to achieve national defense and security objectives.
-
C.
English naval ship
An English naval ship is a seafaring war vessel commissioned by the English crown, designed, armed, and crewed for maritime defense, power projection, and control of sea lanes.
-
D.
British auxiliary officer
A British auxiliary officer is a part-time or non-regular commissioned or non-commissioned member of the British armed forces who supports regular units in military, security, or administrative roles, often during emergencies or wartime.
-
E.
Royal Navy tradition
Royal Navy tradition encompasses the long-established customs, ceremonies, values, and practices that shape the identity, discipline, and heritage of the United Kingdom’s naval service.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.