Triple
T29024218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardwell |
E737541
|
entity |
| Predicate | announcedHiatusFromTouring |
P54927
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Hardwell, announcedHiatusFromTouring, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedHiatusFromTouring Context triple: [Hardwell, announcedHiatusFromTouring, 2018]
-
A.
announcedHiatus
chosen
Indicates that an entity has publicly declared a temporary pause or suspension in its usual activities or operations.
-
B.
hiatusSincePreviousAlbum
Indicates the length of time that has passed between the release of the previous album and the current one.
-
C.
temporarilyRetiredFromSetlistsBy
Indicates that a song or piece has been removed from live setlists by a performer or group for a limited, non-permanent period.
-
D.
releasedAfterHiatusOf
Indicates that one entity (typically a work or product) was released following a preceding break or hiatus of the other entity (such as an artist, series, or organization).
-
E.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 9:51 a.m.