Triple
T27970500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brass Eye |
E706340
|
entity |
| Predicate | includesSpecialEpisode |
P16447
|
FINISHED |
| Object | Brass Eye Special: Paedogeddon! |
—
|
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: Brass Eye Special: Paedogeddon! | Statement: [Brass Eye, includesSpecialEpisode, Brass Eye Special: Paedogeddon!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSpecialEpisode Context triple: [Brass Eye, includesSpecialEpisode, Brass Eye Special: Paedogeddon!]
-
A.
includesSpecialEpisodes
chosen
Indicates that the subject collection or series contains one or more special, non-regular episodes.
-
B.
specialEpisodeAirDate
Indicates the calendar date on which a special episode is broadcast or made available to the public.
-
C.
includesPilotEpisode
Indicates that one entity (such as a series or collection) contains or features a pilot episode as part of its content.
-
D.
isEpisodeOfType
Indicates that an episode belongs to or is classified under a specific type or category.
-
E.
hasEpisodeAbout
Indicates that a particular episode (such as of a show, podcast, or series) focuses on, discusses, or is centered around a specified subject or topic.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 27, 2026, 7:37 p.m.