Triple
T4667056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Pelham |
E102870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate military officer |
C449
|
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: Confederate military officer Context triple: [John Pelham, instanceOf, Confederate military officer]
-
A.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
B.
Boer military leader
A Boer military leader is a commander from the Dutch-descended Afrikaner communities of South Africa who directs and organizes Boer forces in military campaigns, often characterized by mobile, guerrilla-style warfare.
-
C.
paramilitary leader
A paramilitary leader is an individual who commands, organizes, and directs a non-regular, often politically motivated armed group that operates with military-style structure, tactics, and discipline outside or alongside official state forces.
-
D.
Mexican general
A Mexican general is a high-ranking military officer in Mexico’s armed forces responsible for leading troops, planning and executing military operations, and contributing to national defense and security strategy.
-
E.
American colonial soldier
An American colonial soldier is an armed militiaman or regular enlisted in the British American colonies who participated in local defense, frontier warfare, and major conflicts such as the French and Indian War and the American Revolutionary War.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:15 p.m.