Triple
T33493943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Symphony Orchestra |
E857813
|
entity |
| Predicate | mainConcertVenue |
P191599
|
FINISHED |
| Object | Esplanade Concert 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: Esplanade Concert Hall | Statement: [Singapore Symphony Orchestra, mainConcertVenue, Esplanade Concert Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConcertVenue Context triple: [Singapore Symphony Orchestra, mainConcertVenue, Esplanade Concert Hall]
-
A.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
B.
internationalVenueFor
Indicates that a location serves as a host or site for events, activities, or functions involving participants or audiences from multiple countries.
-
C.
largestVenueOf
Indicates that one venue is the largest (typically by capacity, area, or scale) among a specified set or within a particular context.
-
D.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
E.
originalPerformanceVenue
Indicates the venue where a performance was first originally presented or premiered.
- F. None of above. chosen
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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.