Triple
T4749511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British fleet at Porto Bello |
E105443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military unit |
C2497
|
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: British military unit Context triple: [British fleet at Porto Bello, instanceOf, British military unit]
-
A.
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.
-
B.
branch of the British Indian Army
A branch of the British Indian Army is a major organizational subdivision responsible for a specific type of military function or service, such as infantry, cavalry, artillery, or engineering, within the colonial armed forces of British India.
-
C.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
-
D.
British East India Company regiment
A British East India Company regiment was a military unit raised, organized, and maintained by the Company in India to protect its commercial interests, enforce territorial control, and support colonial governance.
-
E.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.