Triple
T33493944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Symphony Orchestra |
E857813
|
entity |
| Predicate | secondaryConcertVenue |
P48888
|
FINISHED |
| Object | Victoria 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: Victoria Concert Hall | Statement: [Singapore Symphony Orchestra, secondaryConcertVenue, Victoria Concert Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryConcertVenue Context triple: [Singapore Symphony Orchestra, secondaryConcertVenue, Victoria Concert Hall]
-
A.
secondTestVenue
Indicates that an entity serves as the second venue or location associated with a particular test or testing event.
-
B.
secondEventLocation
Indicates the location where the second event in a sequence takes place.
-
C.
secondaryStadium
Indicates that an entity serves as an additional or backup stadium associated with another primary stadium or team.
-
D.
mainConcertVenue
Indicates that a location serves as the primary venue where a concert or musical event is held.
-
E.
secondaryTheater
chosen
Indicates that an entity serves as a secondary or supporting theater or venue in relation to a primary one.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:38 a.m.