Triple
T33763398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Want Out |
E865169
|
entity |
| Predicate | isOftenPerformedWithAudienceParticipation |
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: [I Want Out, isOftenPerformedWithAudienceParticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPerformedWithAudienceParticipation Context triple: [I Want Out, isOftenPerformedWithAudienceParticipation, true]
-
A.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
B.
isAudienceChoiceFor
Indicates that one entity represents a choice, option, or selection available to an audience in relation to another entity.
-
C.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
D.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
E.
sungToAudience
Indicates that a performance or song was vocally delivered in front of and directed toward an audience.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.