Triple
T27102330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dial of Destiny |
E686473
|
entity |
| Predicate | isLinkedToCharacter |
P63755
|
FINISHED |
| Object | Basil Shaw |
—
|
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: Basil Shaw | Statement: [Dial of Destiny, isLinkedToCharacter, Basil Shaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinkedToCharacter Context triple: [Dial of Destiny, isLinkedToCharacter, Basil Shaw]
-
A.
associatedWithCharacterRole
chosen
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
B.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
C.
fictionalCharacterAssociatedWith
Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
-
D.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
E.
connectsCharacter
Indicates that one character is linked or associated with another in some meaningful way.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:48 a.m.