Triple

T34748818
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Saint Petersburg (1793) E1001710 entity
Predicate imposesCostOn P7925 FINISHED
Object Polish–Lithuanian Commonwealth NE NERFINISHED

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: Polish–Lithuanian Commonwealth | Statement: [Treaty of Saint Petersburg (1793), imposesCostOn, Polish–Lithuanian Commonwealth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: imposesCostOn
Context triple: [Treaty of Saint Petersburg (1793), imposesCostOn, Polish–Lithuanian Commonwealth]
  • A. hasCost
    Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
  • B. imposes chosen
    Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
  • C. increasedCostFor
    Indicates that one entity causes or experiences a rise in the cost associated with another entity or activity.
  • D. economicCost
    Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
  • E. coversCosts
    Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
  • F. None of above.

Provenance (3 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_69f76db0367081909b57c50a7fb03025 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77ffa6b68819090257fed3802c239 completed May 3, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69f7795978c481909e152cd1bd02dd07 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.