Triple
T15006767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Bureau of Statistics |
E377729
|
entity |
| Predicate | notableCensusYear |
P292
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Australian Bureau of Statistics, notableCensusYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCensusYear Context triple: [Australian Bureau of Statistics, notableCensusYear, 2011]
-
A.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
B.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
C.
notableElectionYear
Indicates that a particular year is recognized as significant or noteworthy in the context of an election involving the given entity.
-
D.
censusReportedIn
Indicates that information about a population or demographic count is documented or recorded in a specific census.
-
E.
notableProjectYear
Indicates the year in which a notable project associated with an entity took place, was created, or was prominently recognized.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded73348d4819091d9e7f1b0fed822 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.