Triple
T3010444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English forces under Richard Nicolls |
E82204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Navy and Army contingent |
C12131
|
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: Royal Navy and Army contingent Context triple: [English forces under Richard Nicolls, instanceOf, Royal Navy and Army contingent]
-
A.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
B.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
C.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
-
D.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
E.
Royal Navy station
A Royal Navy station is a geographically defined area or shore establishment from which Royal Navy forces are administered, supported, and directed for operations within a particular region.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.