Triple
T991739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to Bedlam |
E21405
|
entity |
| Predicate | followedByReleaseYear |
P22827
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Back to Bedlam, followedByReleaseYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByReleaseYear Context triple: [Back to Bedlam, followedByReleaseYear, 2007]
-
A.
sequelReleaseYear
Indicates the calendar year in which a sequel to an original work is released.
-
B.
laterSeriesYear
Indicates that one entity is a series whose release or production year is later than that of another related series.
-
C.
sequelSpecialReleaseYear
Indicates the year in which a sequel received a special or re-released version.
-
D.
laterProducedBy
Indicates that something is produced or created by an entity at a later time than some referenced or implied production event.
-
E.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c25e5081909ff1ada6b8bf617a |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.