Triple
T20154058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian federal budget |
E491507
|
entity |
| Predicate | financialYearEnd |
P4827
|
FINISHED |
| Object | 30 June |
—
|
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: 30 June | Statement: [Australian federal budget, financialYearEnd, 30 June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialYearEnd Context triple: [Australian federal budget, financialYearEnd, 30 June]
-
A.
fiscalYearEnd
chosen
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
B.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
-
C.
yearEndListInclusion
Indicates that an entity is included in a list or ranking that is specifically compiled for the end of a given year.
-
D.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
E.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667de9bec8190836887c86dbcf28d |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.