Triple
T26023293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Flight of the Bumblebee |
E647212
|
entity |
| Predicate | workNumberInOpera |
P158257
|
FINISHED |
| Object | orchestral interlude between scenes |
—
|
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: orchestral interlude between scenes | Statement: [The Flight of the Bumblebee, workNumberInOpera, orchestral interlude between scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInOpera Context triple: [The Flight of the Bumblebee, workNumberInOpera, orchestral interlude between scenes]
-
A.
workNumberInOpera
chosen
Indicates the numerical position or catalog number assigned to a specific work within an opera.
-
B.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
C.
workFromOpera
Indicates that an entity performs work or operates starting from, or based in, an opera-related context or location.
-
D.
workNumberWithinOratorio
Indicates that a specific work is identified by its numerical position within an oratorio.
-
E.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e8c0a08190a34cad51a19e92de |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:04 a.m.