Triple
T36540471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The TV Movie |
E900705
|
entity |
| Predicate | featuresRegenerationFrom |
P121846
|
FINISHED |
| Object | Seventh Doctor |
E382593
|
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: Seventh Doctor | Statement: [The TV Movie, featuresRegenerationFrom, Seventh Doctor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRegenerationFrom Context triple: [The TV Movie, featuresRegenerationFrom, Seventh Doctor]
-
A.
featuresRegeneration
Indicates that an entity possesses the ability to regenerate or regrow lost or damaged parts.
-
B.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
C.
regenerationSource
chosen
Indicates that one entity serves as the origin, cause, or provider for the restoration or regrowth of another entity.
-
D.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
E.
regenerationAssociatedWith
Indicates an association between a regeneration process and a related factor, condition, or entity involved in or linked to that regenerative activity.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e160afd4c8190a1e15db8614b59e4 |
completed | June 26, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.