Triple
T15916957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate River Defense Fleet |
E385993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Navy unit |
C20348
|
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: Confederate States Navy unit Context triple: [Confederate River Defense Fleet, instanceOf, Confederate States Navy unit]
-
A.
naval unit
chosen
A naval unit is an organized group of maritime military assets—such as ships, submarines, aircraft, and personnel—structured to conduct operations and missions at sea.
-
B.
Continental Navy ship
A Continental Navy ship is a naval vessel commissioned by the Continental Congress during the American Revolutionary War to conduct maritime warfare, protect commerce, and challenge British naval power.
-
C.
ship of the Continental Navy
A ship of the Continental Navy is a naval vessel commissioned by the Continental Congress during the American Revolutionary War to conduct maritime warfare, protect commerce, and challenge British naval power.
-
D.
United States Navy construction force
The United States Navy construction force, commonly known as the Seabees, is a military engineering organization responsible for building and maintaining naval bases, airfields, and other critical infrastructure in support of naval and joint operations worldwide.
-
E.
United States Coast Guard unit
A United States Coast Guard unit is an organized group within the Coast Guard, such as a cutter, station, air station, or specialized team, that performs specific missions related to maritime safety, security, and environmental protection.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.