Triple
T18566170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS 15 Revenue from Contracts with Customers |
E453764
|
entity |
| Predicate | earlyApplicationPermitted |
P104189
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [IFRS 15 Revenue from Contracts with Customers, earlyApplicationPermitted, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyApplicationPermitted Context triple: [IFRS 15 Revenue from Contracts with Customers, earlyApplicationPermitted, Yes]
-
A.
earlyUse
Indicates that an entity is used or adopted at an unusually early time or stage relative to a typical or expected point of use.
-
B.
mayApply
chosen
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
-
C.
secondaryApplication
Indicates that an additional, follow-up application is submitted or required beyond an initial primary application.
-
D.
earlyActivity
Indicates that an entity begins or performs a specified activity earlier than a usual, expected, or referenced time.
-
E.
onlineApplication
Indicates that an application or request is submitted, processed, or managed through an online or web-based system.
- 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.