Triple
T18071568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenzer |
E432441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Habsburg military formation |
C39785
|
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: Habsburg military formation Context triple: [Grenzer, instanceOf, Habsburg military formation]
-
A.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
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.
institution of Austria-Hungary
An institution of Austria-Hungary is an organized body or establishment—political, legal, military, educational, or cultural—created or officially recognized within the dual monarchy of Austria-Hungary (1867–1918) to perform specific governmental or societal functions.
-
D.
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.
-
E.
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.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.