Triple
T33493960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Symphony Orchestra |
E857813
|
entity |
| Predicate | performsEducationConcerts |
P197209
|
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, performsEducationConcerts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsEducationConcerts Context triple: [Singapore Symphony Orchestra, performsEducationConcerts, true]
-
A.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
B.
performingArtsDomain
Indicates that the subject operates within, is related to, or is characterized by the field of performing arts.
-
C.
performsMusicFrom
Indicates that one entity presents or executes a musical work that originates from or was created by another entity.
-
D.
providedPianoPerformancesFor
Indicates that one entity supplied or delivered piano performances for the benefit, use, or event of another entity.
-
E.
isEducationalRepertoire
Indicates that something constitutes a set of materials, activities, or practices used for educational or instructional purposes.
- 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_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 1, 2026, 1:38 a.m.