Triple
T27051072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra 2009 project |
E684773
|
entity |
| Predicate | finalEventVenue |
P59030
|
FINISHED |
| Object | Isaac Stern Auditorium, Carnegie Hall |
—
|
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: Isaac Stern Auditorium, Carnegie Hall | Statement: [YouTube Symphony Orchestra 2009 project, finalEventVenue, Isaac Stern Auditorium, Carnegie Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalEventVenue Context triple: [YouTube Symphony Orchestra 2009 project, finalEventVenue, Isaac Stern Auditorium, Carnegie Hall]
-
A.
finalReplayVenue
Indicates the venue where a final match is replayed after an initial final did not produce a decisive result.
-
B.
finalConcertLocation
chosen
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
C.
semiFinalVenue
Indicates the venue where a semifinal match or event takes place.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
finalEventField
Indicates that a field represents the final or ultimate event associated with an entity or process.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 8:14 a.m.