Triple
T14426451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Olney |
E357709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval agreement |
C27712
|
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 agreement Context triple: [Treaty of Olney, instanceOf, medieval agreement]
-
A.
medieval political agreement
chosen
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.
medieval charter
A medieval charter is a formal written document, typically sealed by a ruler or authority, that records and grants legal rights, privileges, or property during the Middle Ages.
-
C.
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.
-
D.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
-
E.
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.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.