Triple
T30303444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Pizarro |
E770710
|
entity |
| Predicate | librettoRevisionsBy |
P151743
|
FINISHED |
| Object | Stephan von Breuning |
—
|
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: Stephan von Breuning | Statement: [Don Pizarro, librettoRevisionsBy, Stephan von Breuning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettoRevisionsBy Context triple: [Don Pizarro, librettoRevisionsBy, Stephan von Breuning]
-
A.
librettoBy
Indicates that a work’s libretto (the text of an opera or similar vocal work) was written by a particular person.
-
B.
bookRevisionsBy
chosen
Indicates that one entity serves as the reviser or editor responsible for updating or modifying the content of a book.
-
C.
librettoStyle
Indicates the stylistic characteristics or manner in which a libretto (the text of an opera or similar work) is written or composed.
-
D.
librettoBasedOn
Indicates that the libretto of a musical or operatic work is derived from, adapted from, or otherwise based on another pre-existing work or source.
-
E.
sharesLibrettoWith
Indicates that two musical or theatrical works use the same libretto text.
- 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_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:49 p.m.