Triple
T19967229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Yeletsky |
E479967
|
entity |
| Predicate | orchestralAccompanimentCharacteristic |
P35077
|
FINISHED |
| Object | lush and expressive |
—
|
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: lush and expressive | Statement: [Prince Yeletsky, orchestralAccompanimentCharacteristic, lush and expressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestralAccompanimentCharacteristic Context triple: [Prince Yeletsky, orchestralAccompanimentCharacteristic, lush and expressive]
-
A.
orchestralArrangement
Indicates that one musical work is arranged or adapted specifically for performance by an orchestra.
-
B.
hasOrchestralFeature
chosen
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
C.
orchestralRole
Indicates the specific function or position an entity holds within an orchestra (e.g., conductor, principal violin, section player).
-
D.
orchestrationIncludes
Indicates that one orchestration contains, incorporates, or makes use of another orchestration as part of its overall structure or process.
-
E.
performedWithOrchestra
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.