Triple
T14445235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger (American privateer tradition) |
E358188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naming convention for privateer vessels |
C16057
|
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: naming convention for privateer vessels Context triple: [Ranger (American privateer tradition), instanceOf, naming convention for privateer vessels]
-
A.
naval nickname
A naval nickname is an informal, often humorous or affectionate moniker given to a ship, sailor, unit, or naval organization that reflects its reputation, characteristics, or history.
-
B.
ship prefix
chosen
A ship prefix is a set of letters placed before a vessel’s name to indicate its type, purpose, or nationality (e.g., "HMS," "USS," "MV").
-
C.
maritime designation
A maritime designation is a formal label or classification assigned to ships, sea areas, routes, or maritime activities to define their status, function, or regulatory conditions.
-
D.
Dutch privateers
Dutch privateers were privately owned, state-authorized armed vessels from the Dutch Republic that attacked and captured enemy ships, especially during the 16th to 18th centuries, to disrupt rival trade and bolster Dutch maritime power.
-
E.
privateer
A privateer is a privately owned, armed vessel (or its captain) authorized by a government during wartime to attack and capture enemy ships for profit under a formal letter of marque.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.