Triple
T2513749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Naval Special Forces |
E52760
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval special forces |
C10260
|
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 special forces Context triple: [French Naval Special Forces, instanceOf, naval special forces]
-
A.
naval infantry
Naval infantry are specialized military forces trained and equipped to conduct amphibious assaults and other combat operations from the sea onto hostile or potentially hostile shores.
-
B.
marine corps
The Marine Corps is a branch of a nation's armed forces specialized in expeditionary and amphibious warfare, trained to rapidly deploy and operate on land, sea, and air in support of national defense objectives.
-
C.
naval reserve force
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.
naval intelligence agency
A naval intelligence agency is an organization within a nation's maritime forces responsible for collecting, analyzing, and disseminating information about foreign naval capabilities, activities, and maritime threats to support naval operations and strategic decision-making.
-
E.
naval air service
A naval air service is a military aviation branch responsible for operating aircraft and related support units in direct support of a nation's navy, including maritime patrol, fleet air defense, anti-submarine warfare, and carrier-based operations.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:46 p.m.