Triple
T18660317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bing Crosby Show |
E456174
|
entity |
| Predicate | featuresRealLifeSpouses |
P132186
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Bing Crosby Show, featuresRealLifeSpouses, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRealLifeSpouses Context triple: [The Bing Crosby Show, featuresRealLifeSpouses, true]
-
A.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
B.
spouseAlsoKnownAs
Indicates that a person’s spouse is referred to by an alternative name or alias.
-
C.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
D.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
hasNamesakeSpouse
Indicates that one entity has a spouse who shares the same name as another specified entity.
- F. None of above. chosen
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_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. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.