Triple
T1355363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominique Horwitz |
E28975
|
entity |
| Predicate | performedAsSingerIn |
P27956
|
FINISHED |
| Object | concerts with symphony orchestras |
—
|
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: concerts with symphony orchestras | Statement: [Dominique Horwitz, performedAsSingerIn, concerts with symphony orchestras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAsSingerIn Context triple: [Dominique Horwitz, performedAsSingerIn, concerts with symphony orchestras]
-
A.
performedSong
Indicates that an entity (such as an artist or performer) has given a performance of a particular song.
-
B.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
C.
sungByCharacter
Indicates that a song or musical piece is performed vocally by a specific character.
-
D.
officialSongPerformer
Indicates that the subject is the performer officially designated as performing the specified song.
-
E.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c28afc848190925d8b2f9aeac12d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c20fd1fc8190977a768b1ed2d23b |
completed | March 1, 2026, 10:47 p.m. |
Created at: March 1, 2026, 7:56 p.m.