Triple
T37894940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Kyser and His Orchestra |
E945249
|
entity |
| Predicate | notableRadioShow |
P2513
|
FINISHED |
| Object | Kay Kyser's Kollege of Musical Knowledge |
E945249
|
NE 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: Kay Kyser's Kollege of Musical Knowledge | Statement: [Kay Kyser and His Orchestra, notableRadioShow, Kay Kyser's Kollege of Musical Knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRadioShow Context triple: [Kay Kyser and His Orchestra, notableRadioShow, Kay Kyser's Kollege of Musical Knowledge]
-
A.
notableShow
chosen
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
B.
notableBroadcast
Indicates that an entity is recognized for having made a significant or widely known broadcast.
-
C.
notableAnnouncer
Indicates that an entity is a well-known or distinguished announcer associated with another entity (such as an event, program, or organization).
-
D.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
E.
notableSyndicatedProgram
Indicates that an entity is recognized for having a prominent or significant syndicated program associated with it.
- F. None of above.
Provenance (4 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cc2b2d0819089452438fd41c600 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.