Triple
T37358362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bei Männern, welche Liebe fühlen |
E927513
|
entity |
| Predicate | operaNumberInCatalogue |
P203879
|
FINISHED |
| Object | K. 620 |
—
|
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: K. 620 | Statement: [Bei Männern, welche Liebe fühlen, operaNumberInCatalogue, K. 620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaNumberInCatalogue Context triple: [Bei Männern, welche Liebe fühlen, operaNumberInCatalogue, K. 620]
-
A.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
-
B.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
C.
operaNumberInKöchelCatalogue
chosen
Indicates the specific Köchel catalogue number assigned to an opera within Mozart’s works.
-
D.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
E.
numberOfOperas
Indicates the total count of operas associated with a given entity (such as a person, organization, or catalog entry).
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:16 p.m.