Triple
T29180543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebesträume |
E739733
|
entity |
| Predicate | commonTeachingUse |
P63933
|
FINISHED |
| Object | advanced piano pedagogy |
—
|
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: advanced piano pedagogy | Statement: [Liebesträume, commonTeachingUse, advanced piano pedagogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonTeachingUse Context triple: [Liebesträume, commonTeachingUse, advanced piano pedagogy]
-
A.
usesInTeaching
chosen
Indicates that an agent employs a particular resource, method, or material as part of their teaching activities.
-
B.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
C.
usedInEducationIn
Indicates that something is employed or applied within educational contexts in a particular place or institution.
-
D.
teachingExample
Indicates that one entity serves as an illustrative or instructional example used to teach or clarify something to another entity.
-
E.
typeOfTeaching
Indicates the specific method or style of teaching used in an instructional context.
- 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_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 11:57 a.m.