Triple
T37522576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty orders and draughts of 1719 |
E932818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical naval 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: historical naval document Context triple: [Admiralty orders and draughts of 1719, instanceOf, historical naval document]
-
A.
historical navy
A historical navy is a maritime military force from a past era, composed of ships, sailors, and supporting infrastructure, organized to project power, protect trade, and conduct warfare at sea.
-
B.
British Admiralty document
chosen
A British Admiralty document is an official record, chart, order, or report produced or authorized by the United Kingdom’s naval command for the administration, operation, or documentation of maritime and naval affairs.
-
C.
naval history project
A naval history project is a structured research and presentation effort focused on analyzing maritime warfare, naval technology, and seafaring cultures across different historical periods.
-
D.
historical political document
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
-
E.
historic ship
A historic ship is a preserved or documented vessel of significant past importance, valued for its cultural, technological, or historical role in maritime heritage.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.