Triple
T30715234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Minds: Beyond Borders |
E782005
|
entity |
| Predicate | hasPilotAsBackdoorEpisodeOf |
P170061
|
FINISHED |
| Object | Criminal Minds |
—
|
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: Criminal Minds | Statement: [Criminal Minds: Beyond Borders, hasPilotAsBackdoorEpisodeOf, Criminal Minds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilotAsBackdoorEpisodeOf Context triple: [Criminal Minds: Beyond Borders, hasPilotAsBackdoorEpisodeOf, Criminal Minds]
-
A.
backdoorPilotEpisodeNumberInSeason
Indicates the specific episode number within a season in which a backdoor pilot for another show occurs.
-
B.
backdoorPilotSeriesSeason
chosen
Indicates that a season of one series contains an episode intended as a backdoor pilot for another series.
-
C.
includesPilotEpisode
Indicates that one entity (such as a series or collection) contains or features a pilot episode as part of its content.
-
D.
pilotProducedFor
Indicates that a pilot episode was created specifically for a particular television show, series, or media project.
-
E.
hasPilot
Indicates that an entity is operated or controlled by a specific pilot.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:35 p.m.