Triple
T32832417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian violin school |
E839726
|
entity |
| Predicate | performanceIdeal |
P175210
|
FINISHED |
| Object | emotional intensity |
—
|
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: emotional intensity | Statement: [Russian violin school, performanceIdeal, emotional intensity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceIdeal Context triple: [Russian violin school, performanceIdeal, emotional intensity]
-
A.
performanceDescribedAs
chosen
Indicates that a performance is characterized or labeled using a particular description or evaluative term.
-
B.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
C.
performanceUse
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
-
D.
performanceTuningBy
Indicates that an entity’s performance has been adjusted, optimized, or fine-tuned by another entity.
-
E.
performanceModel
Indicates a relationship where one entity serves as a performance model that represents, predicts, or characterizes the performance behavior of another entity.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:16 a.m.