Triple
T30370404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German student fraternities (Burschenschaften) |
E772531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional organization |
C46195
|
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: traditional organization Context triple: [German student fraternities (Burschenschaften), instanceOf, traditional organization]
-
A.
traditional association
chosen
A traditional association is a formally organized group of individuals or entities united by shared interests, goals, or professional ties, operating under established rules and customs.
-
B.
traditional state
A traditional state is a political entity whose authority and social order are grounded in long-standing customs, inherited institutions, and historically established power structures rather than modern legal-rational frameworks.
-
C.
traditional council
A traditional council is a governing body composed of community elders or recognized leaders who make decisions, resolve disputes, and preserve cultural norms based on customary laws and practices.
-
D.
traditional account
A traditional account is a conventional explanation or interpretation of an event, practice, or concept that has been widely accepted and passed down over time, often reflecting established beliefs or norms.
-
E.
traditional site
A traditional site is a conventional, often historically or culturally significant location or web presence that follows established structures, layouts, and practices rather than modern, experimental, or highly interactive designs.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.