Triple
T38665809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II. Allegro appassionato |
E940450
|
entity |
| Predicate | premiereWorkCity |
P3172
|
FINISHED |
| Object | Budapest |
—
|
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: Budapest | Statement: [II. Allegro appassionato, premiereWorkCity, Budapest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereWorkCity Context triple: [II. Allegro appassionato, premiereWorkCity, Budapest]
-
A.
premiereWithWork
Indicates that a performance, event, or production debuts at the same time as (or as part of) the first public presentation of a specific work.
-
B.
premiereLocation
chosen
Indicates the place where something (such as a film, play, or event) is first publicly presented or debuted.
-
C.
premiereWork
Indicates that a creative work is the first or debut piece presented or introduced by a particular creator or entity.
-
D.
premiereWorkCommissionedBy
Indicates that the premiere (first performance or presentation) of a work was created specifically on commission from a particular entity.
-
E.
workCity
Indicates the city in which an entity (typically a person) performs their work or job.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.