Triple
T14240362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Master (Doctor Who) |
E352985
|
entity |
| Predicate | hasRegenerations |
P48095
|
FINISHED |
| Object | multiple incarnations |
—
|
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: multiple incarnations | Statement: [The Master (Doctor Who), hasRegenerations, multiple incarnations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegenerations Context triple: [The Master (Doctor Who), hasRegenerations, multiple incarnations]
-
A.
hasMultipleRegenerations
chosen
Indicates that an entity has undergone more than one process of regeneration or renewal.
-
B.
hasRegenerationCycleWith
Indicates that two entities are linked by a recurring regeneration or renewal process that they undergo together or in relation to each other.
-
C.
hasRegenerationType
Indicates the specific kind or method of regeneration associated with an entity.
-
D.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
E.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.