Triple
T13002603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watch What Happens Live with Andy Cohen |
E322204
|
entity |
| Predicate | interactiveElement |
P107777
|
FINISHED |
| Object | viewer call-ins |
—
|
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: viewer call-ins | Statement: [Watch What Happens Live with Andy Cohen, interactiveElement, viewer call-ins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactiveElement Context triple: [Watch What Happens Live with Andy Cohen, interactiveElement, viewer call-ins]
-
A.
interactive
Indicates that one entity engages in reciprocal or two-way communication or action with another entity.
-
B.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
C.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
D.
userInteractionModel
Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
-
E.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9828748190b2ad9ea29180b7d3 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e74283c819082e69ac3554fa7d8 |
completed | April 10, 2026, 10:49 p.m. |
Created at: April 9, 2026, 8:47 p.m.