Triple
T18746798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palatine Guard |
E458426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Papal military unit |
C41568
|
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: Papal military unit Context triple: [Palatine Guard, instanceOf, Papal military unit]
-
A.
Italo-Spanish military unit
An Italo-Spanish military unit is a combined armed force formation composed of Italian and Spanish personnel, resources, and command structures, organized to conduct joint military operations.
-
B.
Spanish imperial military unit
A Spanish imperial military unit is an organized armed formation under the authority of the Spanish Empire, structured for conquest, defense, and control of its territories across Europe and overseas.
-
C.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
D.
Habsburg military formation
A Habsburg military formation is an organized unit or arrangement of troops within the armed forces of the Habsburg Monarchy, structured according to its evolving doctrines, hierarchies, and tactical needs from the early modern period through the empire’s dissolution.
-
E.
medieval military force
A medieval military force is an organized body of armed personnel, including knights, infantry, archers, and support units, raised and commanded by a lord, king, or other authority to wage war, defend territory, and enforce political power during the Middle Ages.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:51 a.m.