Triple
T10613914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian electoral calendar 2023 |
E276071
|
entity |
| Predicate | appliesToYear |
P52032
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Australian electoral calendar 2023, appliesToYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToYear Context triple: [Australian electoral calendar 2023, appliesToYear, 2023]
-
A.
appliesToTaxYear
Indicates the specific tax year or fiscal period to which a tax-related rule, record, or obligation is applicable.
-
B.
applicationYear
Indicates the year in which an application was submitted or made.
-
C.
appliesToElectionYear
chosen
Indicates that something is relevant, valid, or in effect specifically for a given election year.
-
D.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5ca94c8190aa3771925913defc |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.