Triple
T12895499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in D minor, BWV 851 |
E308480
|
entity |
| Predicate | isRecordedAs |
P86544
|
FINISHED |
| Object | piano performance |
—
|
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: piano performance | Statement: [Fugue in D minor, BWV 851, isRecordedAs, piano performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecordedAs Context triple: [Fugue in D minor, BWV 851, isRecordedAs, piano performance]
-
A.
mayBeRecordedAs
Indicates that something can optionally be documented or stored in a recorded form, but is not required to be.
-
B.
reRecordedFrom
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
-
C.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
D.
isRecordedMusic
chosen
Indicates that something is music that has been captured and stored in a recorded form, rather than being performed live in the moment.
-
E.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.