Triple
T12680074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet No. 2 |
E302920
|
entity |
| Predicate | premierePerformerType |
P20624
|
FINISHED |
| Object | string quartet with soprano |
—
|
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: string quartet with soprano | Statement: [String Quartet No. 2, premierePerformerType, string quartet with soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premierePerformerType Context triple: [String Quartet No. 2, premierePerformerType, string quartet with soprano]
-
A.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
premiereType
Indicates the specific kind or category of a premiere event associated with an entity (such as world premiere, national premiere, or regional premiere).
-
C.
premiereSoloist
Indicates that an entity serves as the primary featured solo performer in a particular performance or production.
-
D.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
E.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b32dbc81908101fc5f07e26ed3 |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.