Triple
T29719334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian piano school |
E752002
|
entity |
| Predicate | notablePianist |
P59492
|
FINISHED |
| Object | Sergei Rachmaninoff |
E112412
|
NE 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: Sergei Rachmaninoff | Statement: [Russian piano school, notablePianist, Sergei Rachmaninoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePianist Context triple: [Russian piano school, notablePianist, Sergei Rachmaninoff]
-
A.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
-
B.
notableKeyboardist
chosen
Indicates that the subject is a keyboard player who is widely recognized or distinguished for their skill, influence, or prominence.
-
C.
hasPianist
Indicates that an entity is associated with or features a pianist, typically specifying who performs the piano part in a work, event, or group.
-
D.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
E.
notableConductor
Indicates that the subject is a conductor who is recognized as notable or distinguished in their field.
- F. None of above.
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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26aa7c6d588190be4b051b288ef0d2 |
completed | June 8, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:35 p.m.