Triple
T27690563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARIA Award for Album of the Year (Lonerism) |
E698143
|
entity |
| Predicate | associatedYearOfWorkRelease |
P30914
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [ARIA Award for Album of the Year (Lonerism), associatedYearOfWorkRelease, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedYearOfWorkRelease Context triple: [ARIA Award for Album of the Year (Lonerism), associatedYearOfWorkRelease, 2012]
-
A.
keyWorkReleaseYear
Indicates the year in which a key work (such as a major publication, artwork, or product) was first released.
-
B.
workReleaseYear
chosen
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
-
C.
workReleaseYearOfAppearance
Indicates the year in which a particular work was first released or made its initial appearance.
-
D.
basedInWorkReleaseYear
Indicates that an entity is based in, or derived from, a work that was released in a specified year.
-
E.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: April 27, 2026, 2:51 p.m.