Triple
T29180550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebesträume |
E739733
|
entity |
| Predicate | commonRecordingFormat |
P15615
|
FINISHED |
| Object | solo piano album |
—
|
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: solo piano album | Statement: [Liebesträume, commonRecordingFormat, solo piano album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonRecordingFormat Context triple: [Liebesträume, commonRecordingFormat, solo piano album]
-
A.
liveRecordingFormat
Indicates that the work is a live recording and specifies the format or medium in which that live performance was captured or released.
-
B.
recordingType
chosen
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
C.
recordingMethod
Indicates the technique or process used to capture or record something (such as data, audio, or video).
-
D.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
E.
recordingStyle
Indicates the manner or technique used to capture or document something, such as audio, video, or data.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 11:57 a.m.