Triple
T18566200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS 16 Leases |
E453765
|
entity |
| Predicate | scopeExemption |
P4330
|
FINISHED |
| Object | short-term leases |
—
|
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: short-term leases | Statement: [IFRS 16 Leases, scopeExemption, short-term leases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeExemption Context triple: [IFRS 16 Leases, scopeExemption, short-term leases]
-
A.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
B.
providesExemptionsTo
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
C.
scopeDoesNotInclude
Indicates that a given scope explicitly excludes or does not cover a particular element, condition, or responsibility.
-
D.
exemptionType
chosen
Indicates the specific category or kind of exemption that applies in a given context.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_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. |
Created at: April 10, 2026, 11:43 a.m.