Triple
T35222624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Otto Ehrenfried Nicolai |
E1016999
|
entity |
| Predicate | wroteOpera |
P128607
|
FINISHED |
| Object | Die lustigen Weiber von Windsor |
—
|
NE NERFINISHED |
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: Die lustigen Weiber von Windsor | Statement: [Carl Otto Ehrenfried Nicolai, wroteOpera, Die lustigen Weiber von Windsor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteOpera Context triple: [Carl Otto Ehrenfried Nicolai, wroteOpera, Die lustigen Weiber von Windsor]
-
A.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
-
B.
librettistOfOpera
Indicates that one entity is the librettist who wrote the text (libretto) for the specified opera.
-
C.
composerOfOpera
chosen
Indicates that one entity is the composer who created the opera represented by the other entity.
-
D.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
E.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.