Triple
T32915061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein bürgerliches Trauerspiel |
E841984
|
entity |
| Predicate | genreCharacterization |
P122100
|
FINISHED |
| Object | bourgeois tragedy |
—
|
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: bourgeois tragedy | Statement: [Ein bürgerliches Trauerspiel, genreCharacterization, bourgeois tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreCharacterization Context triple: [Ein bürgerliches Trauerspiel, genreCharacterization, bourgeois tragedy]
-
A.
storyCharacterizedAs
chosen
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
B.
titleCharacterization
Indicates how a title characterizes, describes, or frames an associated entity (such as a work, person, or concept).
-
C.
stanceCharacterization
Indicates how an entity’s attitude, position, or viewpoint toward another entity, claim, or issue is characterized.
-
D.
textualCharacterization
Indicates that one entity provides a descriptive or narrative characterization of another entity, typically in textual form.
-
E.
ownerCharacterization
Indicates how an owner is characterized or described in relation to the entity they own.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:19 a.m.