Triple
T19284076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Underwater Menace |
E482262
|
entity |
| Predicate | serialNumberInSeason |
P135130
|
FINISHED |
| Object | third Second Doctor story produced |
—
|
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: third Second Doctor story produced | Statement: [The Underwater Menace, serialNumberInSeason, third Second Doctor story produced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serialNumberInSeason Context triple: [The Underwater Menace, serialNumberInSeason, third Second Doctor story produced]
-
A.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
B.
seasonNumberInYear
Indicates the specific ordinal position of a season within a given year.
-
C.
franchiseSeasonNumber
Indicates the specific season number assigned to an installment within a larger franchise series.
-
D.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
E.
leagueSeasonNumber
Indicates the ordinal number assigned to a particular season within a league’s sequence of seasons.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0099148190bfec8e8eadc72406 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:30 p.m.