Triple
T2249092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood Bowl Orchestra |
E49573
|
entity |
| Predicate | performsRepertoireBy |
P3738
|
FINISHED |
| Object | film composers |
—
|
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: film composers | Statement: [Hollywood Bowl Orchestra, performsRepertoireBy, film composers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsRepertoireBy Context triple: [Hollywood Bowl Orchestra, performsRepertoireBy, film composers]
-
A.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
originalPerformanceFor
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
-
C.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
D.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
E.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ef74988190a0af51d983cf5658 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.