Triple
T14416714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rus'–Byzantine treaties |
E357471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval diplomatic 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 diplomatic agreement Context triple: [Rus'–Byzantine treaties, instanceOf, medieval diplomatic 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.
church treaty
A church treaty is a formal agreement between religious authorities and secular powers that defines the rights, privileges, and obligations of the church within a given political or legal framework.
-
C.
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.
-
D.
ancient Greek treaty
An ancient Greek treaty is a formal, often inscribed agreement between city-states or powers that establishes terms of peace, alliance, or mutual obligations under the sanction of the gods.
-
E.
World War I–era diplomatic agreement
A World War I–era diplomatic agreement is a formal treaty, pact, or understanding negotiated between states during or immediately surrounding the First World War, aimed at managing alliances, territorial claims, military commitments, or postwar settlements.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.