Triple
T30122440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STANAVFORLANT |
E765594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standing maritime group |
C56164
|
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: standing maritime group Context triple: [STANAVFORLANT, instanceOf, standing maritime group]
-
A.
Marine logistics group
A Marine logistics group is a military organization responsible for planning, coordinating, and executing the supply, maintenance, transportation, medical, and support services that sustain Marine forces in operations.
-
B.
maritime workforce
The maritime workforce comprises all personnel engaged in seafaring, port operations, and related marine industries who ensure the safe, efficient, and sustainable movement of goods and people across waterways.
-
C.
maritime services company
A maritime services company provides specialized support and solutions for the shipping and marine industries, such as vessel operations, logistics, maintenance, and marine consultancy.
-
D.
historical maritime entity
A historical maritime entity is an organization, vessel, or institution from the past that operated on or was fundamentally connected to the sea, shaping or reflecting the maritime activities, trade, warfare, or exploration of its era.
-
E.
maritime classification society
A maritime classification society is an independent organization that establishes and verifies technical standards for the design, construction, and maintenance of ships and offshore structures to ensure their safety and seaworthiness.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.