Triple
T10409455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitry the Impostor |
E245348
|
entity |
| Predicate | typeOfImposture |
P60013
|
FINISHED |
| Object | royal pretender |
—
|
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: royal pretender | Statement: [Dmitry the Impostor, typeOfImposture, royal pretender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfImposture Context triple: [Dmitry the Impostor, typeOfImposture, royal pretender]
-
A.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as another entity.
-
B.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
C.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
D.
usesMasksOrDisguises
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
-
E.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9faa97c819092cadedadabe26bf |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:09 p.m.