Triple
T18566865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAS 40 |
E453778
|
entity |
| Predicate | costModelTreatment |
P132560
|
FINISHED |
| Object | depreciation recognised in accordance with IAS 16 |
—
|
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: depreciation recognised in accordance with IAS 16 | Statement: [IAS 40, costModelTreatment, depreciation recognised in accordance with IAS 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costModelTreatment Context triple: [IAS 40, costModelTreatment, depreciation recognised in accordance with IAS 16]
-
A.
costModel
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
-
B.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
C.
costSharing
Indicates how the financial burden of a cost is divided or shared among multiple parties.
-
D.
costsProvision
Indicates that providing a particular good, service, or resource requires incurring a specified cost.
-
E.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
- 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_69e53aff027481909ca7257967967650 |
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.