Triple
T8494302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mind Transfer |
E201056
|
entity |
| Predicate | fictionalTheme |
P83037
|
FINISHED |
| Object | mind transfer |
—
|
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: mind transfer | Statement: [Mind Transfer, fictionalTheme, mind transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalTheme Context triple: [Mind Transfer, fictionalTheme, mind transfer]
-
A.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
B.
fictionalThemePark
Indicates a relationship where an entity is a theme park that exists only within a fictional or imaginary context.
-
C.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
D.
fictionalMedium
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
-
E.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
- F. None of above. chosen
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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.