Triple
T38213562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Wolf |
E1010620
|
entity |
| Predicate | firstAppearsInSeries |
P48093
|
FINISHED |
| Object | Doctor Who series 1 (2005) |
E1010613
|
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: Doctor Who series 1 (2005) | Statement: [Bad Wolf, firstAppearsInSeries, Doctor Who series 1 (2005)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearsInSeries Context triple: [Bad Wolf, firstAppearsInSeries, Doctor Who series 1 (2005)]
-
A.
firstAppearanceEpisode
Indicates the specific episode in which an entity (such as a character or item) is shown or mentioned for the first time.
-
B.
firstMentionedInSeries
chosen
Indicates the work, episode, or installment in a series where a given entity is introduced or appears for the first time.
-
C.
firstAiredInSeries
Indicates the series in which an episode or show was originally first broadcast.
-
D.
firstAppearanceEpisodeNumber
Indicates the episode number in which an entity (such as a character or item) first appears.
-
E.
firstAppearanceChapter
Indicates the chapter in which an entity (such as a character, item, or concept) is first introduced or appears in a work.
- F. None of above.
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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41854ae88481908c882010f7346540 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.