Triple
T31790067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gniezno Congress |
E811438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval diplomatic summit |
C69
|
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 diplomatic summit Context triple: [Gniezno Congress, instanceOf, medieval diplomatic summit]
-
A.
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.
-
B.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
C.
medieval court
A medieval court is the political and social center surrounding a monarch or noble, where governance, justice, ceremony, and daily life of the ruling elite are conducted.
-
D.
medieval parliament
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.
-
E.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:38 p.m.