Triple
T30469628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophecy |
E775254
|
entity |
| Predicate | associatedWorkPremiereOrchestra |
P143377
|
FINISHED |
| Object | Pittsburgh Symphony Orchestra |
E145558
|
NE 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: Pittsburgh Symphony Orchestra | Statement: [Prophecy, associatedWorkPremiereOrchestra, Pittsburgh Symphony Orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkPremiereOrchestra Context triple: [Prophecy, associatedWorkPremiereOrchestra, Pittsburgh Symphony Orchestra]
-
A.
premiereWorkOrchestra
Indicates that an orchestra is the ensemble that gave the first public performance of a particular work.
-
B.
performedWithOrchestra
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
-
C.
isOrchestralWorkBy
Indicates that a particular orchestral work was created or composed by a specified composer or artist.
-
D.
composerOfPremieredWork
Indicates that one entity is the composer who wrote a work that another entity premiered (first performed or presented).
-
E.
workPremiereEnsemble
chosen
Indicates the ensemble that first performed or premiered a particular work.
- F. None of above.
Provenance (4 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27ac1d20b08190bda63d18a5ca8f85 |
completed | June 9, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:11 p.m.