Triple
T33493961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Symphony Orchestra |
E857813
|
entity |
| Predicate | performsOutreachConcerts |
P197242
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Singapore Symphony Orchestra, performsOutreachConcerts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsOutreachConcerts Context triple: [Singapore Symphony Orchestra, performsOutreachConcerts, true]
-
A.
performsEducationConcerts
Indicates that an entity gives concerts specifically designed for educational purposes or instruction.
-
B.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
C.
hasPublicPerformances
Indicates that an entity conducts or is involved in performances that are open and accessible to the general public.
-
D.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
E.
performedInConcertTours
Indicates that an entity (typically an artist or performer) took part in one or more concert tours.
- 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_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
| PDg | Predicate description generation | batch_69fe7eb31b04819081be531fd9f8a78c |
completed | May 9, 2026, 12:24 a.m. |
Created at: May 1, 2026, 1:38 a.m.