Triple
T29000128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hey Rosetta! |
E736274
|
entity |
| Predicate | hiatusAnnounced |
P54927
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Hey Rosetta!, hiatusAnnounced, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiatusAnnounced Context triple: [Hey Rosetta!, hiatusAnnounced, 2017]
-
A.
hiatusBeforeRelease
Indicates that there is a pause or gap in activity occurring prior to a release event.
-
B.
hiatus
Indicates a temporary pause, break, or interruption in an ongoing process, activity, or sequence.
-
C.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
announcedHiatus
chosen
Indicates that an entity has publicly declared a temporary pause or suspension in its usual activities or operations.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fba62a08190aa64a4ac4b451cee |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:34 a.m.