Triple
T38430702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold von Winkelried |
E903790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swiss folk hero |
C37697
|
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: Swiss folk hero Context triple: [Arnold von Winkelried, instanceOf, Swiss folk hero]
-
A.
11th-century Swiss noble
An 11th-century Swiss noble is a high-ranking landowning aristocrat from the region of present-day Switzerland, wielding military, judicial, and economic power within a feudal hierarchy under larger dynastic or ecclesiastical authorities.
-
B.
Swiss nobleman
chosen
A Swiss nobleman is a male member of the historical or contemporary aristocracy of Switzerland, typically associated with hereditary titles, landownership, and regional political influence within the Swiss cantonal system.
-
C.
Norwegian folk hero
A Norwegian folk hero is a legendary or historical figure from Norway celebrated in folklore and national memory for extraordinary bravery, resistance, or contributions to the people’s cultural identity.
-
D.
Tyrolean rebel leader
A Tyrolean rebel leader is a figure who organizes, inspires, and directs resistance movements in the Tyrol region against occupying or oppressive authorities, often blending local traditions with guerrilla tactics and regional nationalism.
-
E.
Swiss military officer
A Swiss military officer is a commissioned leader in Switzerland’s armed forces responsible for planning, directing, and overseeing military operations, training, and personnel in accordance with Swiss defense policies and neutrality principles.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.