Triple
T16829764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helder Expedition |
E409117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint operation |
C340
|
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: joint operation Context triple: [Helder Expedition, instanceOf, joint operation]
-
A.
joint command
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
B.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
C.
militant operation
A militant operation is a coordinated, often clandestine action carried out by an organized armed group to achieve political, ideological, or territorial objectives through force or the threat of violence.
-
D.
bilateral command
A bilateral command is an instruction or directive that involves or requires coordinated action, agreement, or communication between two distinct parties or sides.
-
E.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.