Triple
T10811856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaffar |
E255119
|
entity |
| Predicate | isCharacterArchetype |
P28952
|
FINISHED |
| Object | evil vizier |
—
|
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: evil vizier | Statement: [Jaffar, isCharacterArchetype, evil vizier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacterArchetype Context triple: [Jaffar, isCharacterArchetype, evil vizier]
-
A.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
B.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
C.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
D.
ArchieType
chosen
Indicates a classification relationship where something is identified as an instance or example of a particular archetype or fundamental type.
-
E.
conceptualCharacter
Indicates that one entity serves as a conceptual or abstract representation of a character associated with 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733eadda48190b2b1183ee60102cb |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.