Triple
T32902284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixtus Beckmesser |
E841642
|
entity |
| Predicate | humiliatedIn |
P154735
|
FINISHED |
| Object | final song contest scene |
—
|
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: final song contest scene | Statement: [Sixtus Beckmesser, humiliatedIn, final song contest scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humiliatedIn Context triple: [Sixtus Beckmesser, humiliatedIn, final song contest scene]
-
A.
ashamedOf
Indicates that one entity feels shame, embarrassment, or guilt because of another entity or because of something associated with that entity.
-
B.
humbledBy
chosen
Indicates that one entity has been made to feel less proud, important, or confident as a result of the actions, qualities, or circumstances associated with another entity.
-
C.
insultedAs
Indicates that one entity directed an insulting or offensive remark or action toward another entity, characterizing the target in a demeaning way.
-
D.
defacedWith
Indicates that one entity has been damaged, marred, or vandalized using another entity as the means or material of defacement.
-
E.
accusesOfMockingHer
Indicates that one entity claims another has mocked or ridiculed her.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.