Triple
T38272324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mostly Mozart Festival Orchestra |
E1021248
|
entity |
| Predicate | associatedFestivalLocation |
P204573
|
FINISHED |
| Object | Avery Fisher Hall |
E216514
|
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: Avery Fisher Hall | Statement: [Mostly Mozart Festival Orchestra, associatedFestivalLocation, Avery Fisher Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFestivalLocation Context triple: [Mostly Mozart Festival Orchestra, associatedFestivalLocation, Avery Fisher Hall]
-
A.
associatedFestivalOrCustom
Indicates a festival or custom that is traditionally linked or related to the given entity.
-
B.
relatedFestivalType
Indicates that one festival is associated with another through a shared or corresponding festival type or category.
-
C.
relatedFestivalSeries
Indicates that one festival is part of, or associated with, a broader festival series or grouping of related festivals.
-
D.
locatedInFestival
Indicates that something exists or takes place within the spatial or organizational boundaries of a specific festival.
-
E.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
- F. None of above. chosen
Provenance (5 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193dcf7088190b982723c072b4f5c |
completed | June 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.