Triple
T33737245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother of Dragons |
E864453
|
entity |
| Predicate | hasAliasForCharacter |
P111852
|
FINISHED |
| Object | Dany |
—
|
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: Dany | Statement: [Mother of Dragons, hasAliasForCharacter, Dany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasForCharacter Context triple: [Mother of Dragons, hasAliasForCharacter, Dany]
-
A.
hasTitleCharacterAlias
Indicates that a title (such as a work or publication) is associated with an alternate or alias name for one of its characters.
-
B.
associatedWithCharacterAlias
chosen
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
C.
hasUnicodeBlockAlias
Indicates that one Unicode block is known or referenced by an alternative name (alias).
-
D.
hasAlienCharacters
Indicates that an entity includes or features characters that are extraterrestrial or non-human in origin.
-
E.
characterCorrespondsTo
Indicates that one character is equivalent to, maps onto, or represents another character in a defined correspondence or mapping.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:44 a.m.