Triple
T25172450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario public accounts |
E630354
|
entity |
| Predicate | accountingBasis |
P117723
|
FINISHED |
| Object | accrual accounting |
—
|
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: accrual accounting | Statement: [Ontario public accounts, accountingBasis, accrual accounting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accountingBasis Context triple: [Ontario public accounts, accountingBasis, accrual accounting]
-
A.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
B.
accrualMethod
Indicates the method or basis by which something (such as interest, revenue, or benefits) is accumulated or recognized over time.
-
C.
accountingTreatment
chosen
Indicates how a transaction, event, or item is recognized, measured, and reported in financial accounts according to specific accounting rules or policies.
-
D.
obligationBasis
Indicates the foundational reason, source, or justification upon which an obligation is based.
-
E.
chargeBasis
Indicates the underlying reason, justification, or legal/contractual basis on which a charge, fee, or accusation is applied.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d485b388190b7b45e9b0c4a9e15 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:21 p.m.