Triple
T33700564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvia |
E863443
|
entity |
| Predicate | dramaticGenreOfWork |
P41553
|
FINISHED |
| Object | comedy of manners |
—
|
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: comedy of manners | Statement: [Sylvia, dramaticGenreOfWork, comedy of manners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticGenreOfWork Context triple: [Sylvia, dramaticGenreOfWork, comedy of manners]
-
A.
dramaType
Indicates the specific category or genre of drama that characterizes an entity or work.
-
B.
dramaticForm
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
-
C.
theatricalGenre
chosen
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
-
D.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
E.
dramaticAction
Indicates an action or event characterized by heightened emotion, tension, or significance that drives or intensifies a dramatic situation or narrative.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.