Triple
T7717646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hüsker Dü |
E174926
|
entity |
| Predicate | releaseYearOfNewDayRising |
P78320
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Hüsker Dü, releaseYearOfNewDayRising, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseYearOfNewDayRising Context triple: [Hüsker Dü, releaseYearOfNewDayRising, 1985]
-
A.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
B.
remakeReleaseYear
Indicates the year in which a remake of an original work was released.
-
C.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
D.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
E.
laterReleaseYear
Indicates that the release year of one entity occurs after the release year of another entity.
- F. None of above. chosen
Provenance (4 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702e9a32081909a153190a62af426 |
completed | March 27, 2026, 10:21 p.m. |
Created at: March 27, 2026, 4:05 p.m.