Triple
T29180551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebesträume |
E739733
|
entity |
| Predicate | commonAnthologyInclusion |
P113658
|
FINISHED |
| Object | collections of Romantic piano favorites |
—
|
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: collections of Romantic piano favorites | Statement: [Liebesträume, commonAnthologyInclusion, collections of Romantic piano favorites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAnthologyInclusion Context triple: [Liebesträume, commonAnthologyInclusion, collections of Romantic piano favorites]
-
A.
hasAnthologyRelation
chosen
Indicates that there is a relationship between entities based on their inclusion in, contribution to, or association with the same anthology or collected work.
-
B.
isAnthologySegmentOf
Indicates that one work or segment is a constituent part or episode within a larger anthology work.
-
C.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
-
D.
numberInAnthology
Indicates the specific position or sequence number that a work occupies within an anthology.
-
E.
notableAnthologyEdited
Indicates that an entity has served as the editor of a notable anthology involving 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:57 a.m.