Triple
T30889328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind Quintet, Op. 10 |
E786852
|
entity |
| Predicate | composerPupilOf |
P7251
|
FINISHED |
| Object | Leoš Janáček |
—
|
NE NERFINISHED |
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: Leoš Janáček | Statement: [Wind Quintet, Op. 10, composerPupilOf, Leoš Janáček]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerPupilOf Context triple: [Wind Quintet, Op. 10, composerPupilOf, Leoš Janáček]
-
A.
successorAsPupil
Indicates that one entity becomes the next pupil or student in place of, or following, another entity.
-
B.
studentComposition
Indicates that one entity is composed of or consists of students, specifying a part-whole relationship where students collectively form the other entity.
-
C.
studiedUnder
chosen
Indicates that one entity received instruction, training, or mentorship from another, typically in an academic or apprenticeship context.
-
D.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
-
E.
studentComponent
Indicates that one entity functions as a student-related part, module, or subunit within a larger system, structure, or 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 8:49 p.m.