Triple
T21686371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Geese (Irish soldiers in exile) |
E535239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military diaspora |
C2458
|
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: historical military diaspora Context triple: [Wild Geese (Irish soldiers in exile), instanceOf, historical military diaspora]
-
A.
medieval migration movement
A medieval migration movement is a large-scale relocation of people during the Middle Ages driven by factors such as warfare, trade, climate change, religious motives, or political upheaval, reshaping demographic, cultural, and economic landscapes across regions.
-
B.
historical occupation
A historical occupation is a type of work or profession that existed in the past, often shaped by the social, economic, and technological conditions of its time and sometimes no longer practiced today.
-
C.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
D.
historical armed forces
chosen
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
E.
transatlantic migration
Transatlantic migration is the large-scale movement of people across the Atlantic Ocean, historically and contemporarily, driven by economic, political, social, and environmental factors that reshape societies on both sides.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:44 p.m.