Triple
T18566219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS 16 Leases |
E453765
|
entity |
| Predicate | transitionApproach |
P129646
|
FINISHED |
| Object | full retrospective approach |
—
|
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: full retrospective approach | Statement: [IFRS 16 Leases, transitionApproach, full retrospective approach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionApproach Context triple: [IFRS 16 Leases, transitionApproach, full retrospective approach]
-
A.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
B.
transitionStrategy
chosen
Indicates the method or plan used to move from one state, phase, or condition to another.
-
C.
transitionReason
Indicates the cause, motivation, or triggering factor behind a change from one state, status, or condition to another.
-
D.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
E.
transitionIssue
Indicates a problem or complication that arises during the process of moving from one state, phase, or condition to another.
- 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.