Triple
T22911931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Been Away Too Long |
E568618
|
entity |
| Predicate | releasedAfterHiatusOf |
P150215
|
FINISHED |
| Object | Soundgarden 1997–2010 hiatus |
—
|
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: Soundgarden 1997–2010 hiatus | Statement: [Been Away Too Long, releasedAfterHiatusOf, Soundgarden 1997–2010 hiatus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedAfterHiatusOf Context triple: [Been Away Too Long, releasedAfterHiatusOf, Soundgarden 1997–2010 hiatus]
-
A.
releasedFollowing
Indicates that one entity was released after another entity, in a subsequent or later release order.
-
B.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
C.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
laterReReleasedBy
Indicates that an entity was re-released at a later time by a specified agent or organization.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18075a0048190bd150e2badeeb7c2 |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.