Triple
T9845977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Munchkin Chorus |
E239342
|
entity |
| Predicate | associatedSongType |
P30697
|
FINISHED |
| Object | show tune |
—
|
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: show tune | Statement: [The Munchkin Chorus, associatedSongType, show tune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSongType Context triple: [The Munchkin Chorus, associatedSongType, show tune]
-
A.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
B.
songType
chosen
Indicates the specific category or genre that a given song belongs to.
-
C.
genreAssociatedWith
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
D.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
E.
notableSongAssociations
Indicates that there are notable or significant associations between an entity and specific songs, such as being referenced by, inspiring, or otherwise prominently linked to those songs.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35ff7848190a8a717773d8654b9 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.