Triple

T32768929
Position Surface form Disambiguated ID Type / Status
Subject Leninsk E837979 entity
Predicate leaseStatus P175100 FINISHED
Object territory leased by Russia from Kazakhstan 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: territory leased by Russia from Kazakhstan | Statement: [Leninsk, leaseStatus, territory leased by Russia from Kazakhstan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: leaseStatus
Context triple: [Leninsk, leaseStatus, territory leased by Russia from Kazakhstan]
  • A. leaseAgreement
    Indicates a contractual relationship in which one party grants another the right to use an asset or property for a specified period in exchange for agreed payments or conditions.
  • B. leaseContext
    Indicates the contextual circumstances, terms, or conditions under which a lease agreement or leasing relationship exists or is interpreted.
  • C. leaseOrigin
    Indicates that one entity is the original source or starting point from which a lease agreement or leasing arrangement is derived.
  • D. leaseBegan
    Indicates that a lease agreement between parties started or came into effect at a specific time.
  • E. leaseNumber
    Indicates the unique identifying number assigned to a specific lease agreement between parties.
  • 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_69f34939857c8190aa9970c51feec1eb completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6cee547108190ad3bc84297d8f516 completed May 3, 2026, 4:28 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
PDg Predicate description generation batch_69f6ce6c76bc8190b865343d3f5810c9 completed May 3, 2026, 4:26 a.m.
Created at: May 1, 2026, 1:13 a.m.