Triple

T6479534
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Copenhagen (1468–1470 marriage arrangements) E146152 entity
Predicate reasonForPledge P71146 FINISHED
Object security for unpaid dowry LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: security for unpaid dowry | Statement: [Treaty of Copenhagen (1468–1470 marriage arrangements), reasonForPledge, security for unpaid dowry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForPledge
Context triple: [Treaty of Copenhagen (1468–1470 marriage arrangements), reasonForPledge, security for unpaid dowry]
  • A. reasonForGrant
    Indicates the justification, purpose, or cause for which a grant is awarded or provided.
  • B. reasonForTribute
    Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
  • C. requiredPledgeFrom
    Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
  • D. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • E. reasonForEnlistment
    Indicates the motivation, cause, or circumstances that led an individual to join a military or similar organized service.
  • F. None of above. chosen

Provenance (4 batches)

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_69c008fec7408190af7b146dc63d9750 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a4e764c819086828bb841f588e0 completed March 22, 2026, 10:16 p.m.
PD Predicate disambiguation batch_69c0673f6d48819080e10c85155c7195 completed March 22, 2026, 10:03 p.m.
PDg Predicate description generation batch_69c06822f73081908e6bb9edecbe77a6 completed March 22, 2026, 10:07 p.m.
Created at: March 22, 2026, 4:51 p.m.