Triple
T16652324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master (Doctor Who) |
E404635
|
entity |
| Predicate | hasIncarnations |
P76487
|
FINISHED |
| Object | multiple regenerations |
—
|
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 regenerations | Statement: [Master (Doctor Who), hasIncarnations, multiple regenerations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncarnations Context triple: [Master (Doctor Who), hasIncarnations, multiple regenerations]
-
A.
hasMultipleIncarnations
chosen
Indicates that an entity exists or appears in more than one distinct form, version, or embodiment over time or context.
-
B.
hasDoctorIncarnation
Indicates that an entity is associated with a specific incarnation or version of the Doctor (e.g., a particular regeneration or portrayal).
-
C.
hasIncarnationsOfGender
Indicates that an entity has different incarnations or forms that each express or are associated with a particular gender.
-
D.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
E.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf7ae7c81908b6807acd8f1669b |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.