Triple
T30303409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orest |
E770709
|
entity |
| Predicate | librettistOfWorkAppearedIn |
P138065
|
FINISHED |
| Object | Hugo von Hofmannsthal |
—
|
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: Hugo von Hofmannsthal | Statement: [Orest, librettistOfWorkAppearedIn, Hugo von Hofmannsthal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettistOfWorkAppearedIn Context triple: [Orest, librettistOfWorkAppearedIn, Hugo von Hofmannsthal]
-
A.
librettistOfWorkAppearingIn
chosen
Indicates that a person is the librettist responsible for the text of a work that appears within a larger composite work or collection.
-
B.
librettistOfParentWork
Indicates that one entity is the librettist who wrote the text (libretto) for the parent work associated with another entity.
-
C.
librettistOfOpera
Indicates that one entity is the librettist who wrote the text (libretto) for the specified opera.
-
D.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
-
E.
librettistNationality
Indicates the relationship between a librettist and the country or nationality with which they are associated.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813bd6bc81909b9b3e89c5ecf129 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:49 p.m.