Triple
T313155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto Barocco |
E7648
|
entity |
| Predicate | musicDriven |
P11860
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Concerto Barocco, musicDriven, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicDriven Context triple: [Concerto Barocco, musicDriven, yes]
-
A.
musicDirectorStart
Indicates the time or event at which someone begins serving as a music director for a group, production, or organization.
-
B.
musicVehicle
Indicates a relationship where a vehicle is associated with or used for playing, broadcasting, or producing music.
-
C.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
D.
musicTradition
Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
-
E.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.