Triple

T18566198
Position Surface form Disambiguated ID Type / Status
Subject IFRS 16 Leases E453765 entity
Predicate retainsForLessors P132551 FINISHED
Object operating lease classification 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: operating lease classification | Statement: [IFRS 16 Leases, retainsForLessors, operating lease classification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: retainsForLessors
Context triple: [IFRS 16 Leases, retainsForLessors, operating lease classification]
  • A. wasLeasedFor
    Indicates that one entity was leased in exchange for a specified payment amount, purpose, or consideration.
  • B. leaseNumber
    Indicates the unique identifying number assigned to a specific lease agreement between parties.
  • C. leaseContext
    Indicates the contextual circumstances, terms, or conditions under which a lease agreement or leasing relationship exists or is interpreted.
  • D. tenantsEnd
    Indicates that a tenancy or lease relationship between parties comes to an end at a specified time or under certain conditions.
  • E. isPrivatelyLeased
    Indicates that an entity is under a lease agreement held by a private (non-governmental) party rather than being publicly owned or leased.
  • 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53afe3ee081909eeee62c889948f4 completed April 19, 2026, 8:28 p.m.
PD Predicate disambiguation batch_69e478c16e0c8190b03966aa23c395a6 completed April 19, 2026, 6:40 a.m.
PDg Predicate description generation batch_69e484121cd48190bf583b4c94636a30 completed April 19, 2026, 7:28 a.m.
Created at: April 10, 2026, 11:43 a.m.