Triple
T18665122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Navy Reserve units in Atlantic Canada |
E456304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Naval reserve formation |
C6315
|
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 reserve formation Context triple: [Royal Canadian Navy Reserve units in Atlantic Canada, instanceOf, Naval reserve formation]
-
A.
U.S. Navy formation
A U.S. Navy formation is an organized arrangement of naval vessels or aircraft maneuvering together under a unified command to achieve tactical, operational, or ceremonial objectives at sea or in the air.
-
B.
Imperial Russian Navy formation
An Imperial Russian Navy formation is an organized grouping of naval vessels, aircraft, and supporting units structured under a unified command to conduct maritime operations for the Russian Empire.
-
C.
naval reserve force
chosen
A naval reserve force is a component of a nation's navy composed of trained personnel who serve part-time and can be mobilized to support or augment regular naval operations during emergencies, conflicts, or special missions.
-
D.
French naval formation
A French naval formation is an organized arrangement of French warships and support vessels maneuvered together under unified command to achieve specific tactical or strategic objectives at sea.
-
E.
maritime security formation
A maritime security formation is an organized grouping of naval and coast guard assets coordinated to protect sea lanes, coastal areas, and maritime interests from threats such as piracy, terrorism, smuggling, and unauthorized incursions.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.