Triple
T12742998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congress of Gniezno |
E304533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval political assembly |
C11597
|
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: medieval political assembly Context triple: [Congress of Gniezno, instanceOf, medieval political assembly]
-
A.
medieval parliament
chosen
A medieval parliament is an assembly of nobles, clergy, and sometimes commoners convened by a monarch to advise on governance, consent to taxation, and address matters of law and policy.
-
B.
medieval political agreement
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
-
C.
medieval political faction
A medieval political faction is an organized group of nobles, clergy, or urban elites who align around shared interests, loyalties, or claims to power, competing and negotiating within the feudal and dynastic structures of the Middle Ages.
-
D.
nobility assembly house
A nobility assembly house is a formal building where members of the aristocracy gather for political deliberation, social events, and the administration of noble affairs.
-
E.
deliberative assembly
A deliberative assembly is a group of people who meet to discuss, debate, and decide on matters of common concern, typically following formal rules of procedure.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.