Triple
T25192290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titipu |
E630902
|
entity |
| Predicate | hasMusicalNumbersSetIn |
P115418
|
FINISHED |
| Object | “A Wandering Minstrel I” |
—
|
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: “A Wandering Minstrel I” | Statement: [Titipu, hasMusicalNumbersSetIn, “A Wandering Minstrel I”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalNumbersSetIn Context triple: [Titipu, hasMusicalNumbersSetIn, “A Wandering Minstrel I”]
-
A.
hasMusicalNumberIn
chosen
Indicates that a musical number (song or performance) appears within or is featured in a specific work, scene, or production.
-
B.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
C.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
hasEnsembleNumbers
Indicates that an entity is associated with one or more ensemble numbers used to identify it within a grouped or collective 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 12:45 p.m.