Triple
T30714444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Who: The Roundheads |
E781983
|
entity |
| Predicate | seriesNumberWithinRange |
P131220
|
FINISHED |
| Object | Virgin Missing Adventures |
—
|
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: Virgin Missing Adventures | Statement: [Doctor Who: The Roundheads, seriesNumberWithinRange, Virgin Missing Adventures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesNumberWithinRange Context triple: [Doctor Who: The Roundheads, seriesNumberWithinRange, Virgin Missing Adventures]
-
A.
belongsToSeriesRange
chosen
Indicates that something is part of, or falls within, a specified series or sequence range.
-
B.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
serialNumberRange
Indicates that there is a specified range of serial numbers within which the related entities or items fall.
-
D.
articleNumberRange
Indicates that something is associated with or falls within a specified range of article numbers.
-
E.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
- 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_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.