Triple
T38599564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Despina |
E934170
|
entity |
| Predicate | dramaticArchetype |
P102015
|
FINISHED |
| Object | servant trickster |
—
|
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: servant trickster | Statement: [Despina, dramaticArchetype, servant trickster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticArchetype Context triple: [Despina, dramaticArchetype, servant trickster]
-
A.
dramaticCharacter
Indicates that one entity is a character or role that appears within the dramatic work, performance, or narrative represented by the other entity.
-
B.
dramaticTrait
Indicates that an entity possesses a tendency to behave or express itself in an exaggerated, theatrical, or emotionally intense manner.
-
C.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
D.
dramaticStructureRole
Indicates the specific function or role an element plays within the overall dramatic structure of a narrative or performance.
-
E.
usesCharacterArchetype
chosen
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.