Triple
T29020636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duffless |
E737441
|
entity |
| Predicate | chronologicalSuccessorEpisode |
P45886
|
FINISHED |
| Object | Last Exit to Springfield |
—
|
NE NERFINISHED |
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: Last Exit to Springfield | Statement: [Duffless, chronologicalSuccessorEpisode, Last Exit to Springfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalSuccessorEpisode Context triple: [Duffless, chronologicalSuccessorEpisode, Last Exit to Springfield]
-
A.
followsEpisode
chosen
Indicates that one episode occurs directly after another in a sequence or series.
-
B.
subsequentEpisodesReleased
Indicates that additional episodes following an initial one have been made available or published.
-
C.
associatedEpisode
Indicates that one entity is linked or connected to a particular episode as its related or relevant installment.
-
D.
followedBySeason
Indicates that one season occurs immediately after another in chronological order.
-
E.
successorSeries
Indicates that one series directly follows another in sequence, continuing or extending it as its successor.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 9:49 a.m.