Triple
T38690718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of the Reconquista |
E949254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval diplomatic practice |
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 diplomatic practice Context triple: [Treaties of the Reconquista, instanceOf, medieval diplomatic practice]
-
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.
diplomatic history
Diplomatic history is the study of how states and other international actors conduct relations, negotiate agreements, and manage conflicts over time through diplomacy and foreign policy.
-
C.
set of diplomatic customs
A set of diplomatic customs is a collection of established, often unwritten, practices and protocols that guide the behavior, communication, and ceremonial interactions between states and their representatives.
-
D.
medieval transaction
A medieval transaction is an exchange of goods, services, land, or obligations formalized through customary practices, feudal relationships, and often religious or royal authority rather than standardized monetary systems and contracts.
-
E.
medieval polity
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.