Triple
T16437188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good to Be Bad |
E399206
|
entity |
| Predicate | followedByReleaseDate |
P104670
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Good to Be Bad, followedByReleaseDate, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByReleaseDate Context triple: [Good to Be Bad, followedByReleaseDate, 2011]
-
A.
followedByReleaseYear
Indicates that one item is immediately succeeded by another item in terms of release year.
-
B.
followsInReleaseChronology
chosen
Indicates that one entity is released after another in a chronological sequence of releases.
-
C.
laterReleasedIn
Indicates that one entity was released at a later time or date than another entity, establishing a chronological order between their release events.
-
D.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
E.
laterReleases
Indicates that one release, version, or publication occurs after another in time.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba49f3481908e7ea62467ef5813 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.