Triple
T18660318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bing Crosby Show |
E456174
|
entity |
| Predicate | starIsSinger |
P5563
|
FINISHED |
| Object | Bing Crosby as legendary crooner |
—
|
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: Bing Crosby as legendary crooner | Statement: [The Bing Crosby Show, starIsSinger, Bing Crosby as legendary crooner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starIsSinger Context triple: [The Bing Crosby Show, starIsSinger, Bing Crosby as legendary crooner]
-
A.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
-
B.
starredActor
chosen
Indicates that an actor performed a leading or significant role in a particular production or work.
-
C.
isSungBy
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
D.
starKnownAs
Indicates that a particular star is referred to or identified by a specific name or designation.
-
E.
notableStar
Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508a30248190abdb51e345168849 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.