Triple
T32993495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoned Love |
E844155
|
entity |
| Predicate | hasNotableTVPerformance |
P28040
|
FINISHED |
| Object | The Ed Sullivan Show |
—
|
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: The Ed Sullivan Show | Statement: [Stoned Love, hasNotableTVPerformance, The Ed Sullivan Show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTVPerformance Context triple: [Stoned Love, hasNotableTVPerformance, The Ed Sullivan Show]
-
A.
hasNotableTelevisionSeries
Indicates that an entity is associated with one or more television series that are considered notable or significant.
-
B.
hasNotableFilm
Indicates that an entity is associated with a film that is considered significant, well-known, or particularly noteworthy.
-
C.
hasNotableMultipleAppearances
Indicates that an entity appears multiple times in a context or medium in a way considered significant or noteworthy.
-
D.
hasNotablePerformanceIn
chosen
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
E.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
Created at: May 1, 2026, 1:22 a.m.