Triple
T3659786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tenth Planet |
E77619
|
entity |
| Predicate | hasMissingEpisode |
P50201
|
FINISHED |
| Object | episode 4 |
—
|
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: episode 4 | Statement: [The Tenth Planet, hasMissingEpisode, episode 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissingEpisode Context triple: [The Tenth Planet, hasMissingEpisode, episode 4]
-
A.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
B.
missedSeason
Indicates that an entity did not participate in or was absent for a particular season of an activity, event, or series.
-
C.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
D.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
E.
includesSpecialEpisodes
Indicates that the subject collection or series contains one or more special, non-regular episodes.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d5e5f881909c7c105827d41071 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.