Triple
T35365858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindhorn |
E1021625
|
entity |
| Predicate | hasTVShowWithinFilm |
P183061
|
FINISHED |
| Object | Mindhorn (fictional TV series) |
E1021623
|
NE 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: Mindhorn (fictional TV series) | Statement: [Mindhorn, hasTVShowWithinFilm, Mindhorn (fictional TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTVShowWithinFilm Context triple: [Mindhorn, hasTVShowWithinFilm, Mindhorn (fictional TV series)]
-
A.
hasFictionalFilmWithinPlay
Indicates that within a theatrical play, there is a fictional film that exists or is depicted as part of the play’s narrative or structure.
-
B.
hasAssociatedTVSeries
Indicates that one entity is linked to another entity that is a related or derived television series.
-
C.
hasPartInFilmSeries
Indicates that an entity participates in or contributes to one or more installments within a specific film series.
-
D.
hasTVSeriesAdaptation
Indicates that a work has been adapted into a television series.
-
E.
alsoFilmedIn
Indicates that the same film or video production was additionally shot or recorded in another specified location.
- F. None of above. chosen
Provenance (5 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823df0edc819085fb6a0efaf6f7a4 |
completed | June 21, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.