Triple
T33700563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvia |
E863443
|
entity |
| Predicate | dramaticDeviceUsed |
P73293
|
FINISHED |
| Object | cross-dressing |
—
|
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: cross-dressing | Statement: [Sylvia, dramaticDeviceUsed, cross-dressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticDeviceUsed Context triple: [Sylvia, dramaticDeviceUsed, cross-dressing]
-
A.
hasDramaticTechnique
chosen
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
B.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
C.
dramaticConvention
Indicates a relationship where a particular technique, device, or practice is recognized and used as an accepted convention within dramatic or theatrical storytelling.
-
D.
dramaticFeature
Indicates that one entity possesses or exhibits a notable dramatic characteristic or element in relation to another entity.
-
E.
metaTheatricalDevice
Indicates a relationship where a theatrical work self-consciously draws attention to its own nature as theater, performance, or fiction (e.g., breaking the fourth wall, play-within-a-play).
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8ca3808190be2fd9e5fb4c2146 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.