Triple
T29530173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Singing Rooms |
E749177
|
entity |
| Predicate | workTypeDetail |
P131299
|
FINISHED |
| Object | concerto for violin, choir, and orchestra |
—
|
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: concerto for violin, choir, and orchestra | Statement: [The Singing Rooms, workTypeDetail, concerto for violin, choir, and orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTypeDetail Context triple: [The Singing Rooms, workTypeDetail, concerto for violin, choir, and orchestra]
-
A.
workDetail
chosen
Indicates a detailed specification or description of the work associated with an entity or activity.
-
B.
workTypeOfSetting
Indicates the type or nature of work activity that characterizes or occurs within a particular setting.
-
C.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
D.
featuresWorkType
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
E.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:52 p.m.