Triple
T4621298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gall |
E100990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century military leader |
C16128
|
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: 19th-century military leader Context triple: [Gall, instanceOf, 19th-century military leader]
-
A.
ancient Greek military leader
An ancient Greek military leader is a high-ranking commander responsible for organizing, directing, and strategizing the actions of Greek city-state or coalition forces in warfare.
-
B.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
C.
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.
-
D.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
E.
military reformer
A military reformer is an individual who critically evaluates existing armed forces structures, doctrines, and practices and implements innovative changes to improve their effectiveness, efficiency, and adaptability.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.