Triple
T37501636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Bet! |
E931976
|
entity |
| Predicate | usesAudienceParticipation |
P45833
|
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: [You Bet!, usesAudienceParticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAudienceParticipation Context triple: [You Bet!, usesAudienceParticipation, true]
-
A.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
B.
engagesAudienceAs
Indicates that one entity actively captures, involves, or holds the attention of an audience in the manner or role specified by another entity.
-
C.
isAudienceChoiceFor
Indicates that one entity represents a choice, option, or selection available to an audience in relation to another entity.
-
D.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
E.
allowsParticipationIn
Indicates that one entity grants another entity the right or permission to take part in a specific activity, event, or process.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.