Triple
T25158219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Champion |
E626371
|
entity |
| Predicate | hasIncarnation |
P58566
|
FINISHED |
| Object | Elric of Melniboné |
—
|
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: Elric of Melniboné | Statement: [Eternal Champion, hasIncarnation, Elric of Melniboné]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncarnation Context triple: [Eternal Champion, hasIncarnation, Elric of Melniboné]
-
A.
hasDoctorIncarnation
Indicates that an entity is associated with a specific incarnation or version of the Doctor (e.g., a particular regeneration or portrayal).
-
B.
hasMultipleIncarnations
Indicates that an entity exists or appears in more than one distinct form, version, or embodiment over time or context.
-
C.
succeedsIncarnation
Indicates that one incarnation directly follows and replaces another in a temporal or sequential order.
-
D.
incarnationOf
chosen
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
E.
introducesIncarnation
Indicates that one entity brings about, initiates, or presents the embodiment or incarnation of another entity in a concrete or manifest form.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:31 a.m.