Triple
T11838398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockin’ Country Sunday |
E281582
|
entity |
| Predicate | liveAudienceType |
P89961
|
FINISHED |
| Object | stadium audience |
—
|
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: stadium audience | Statement: [Rockin’ Country Sunday, liveAudienceType, stadium audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveAudienceType Context triple: [Rockin’ Country Sunday, liveAudienceType, stadium audience]
-
A.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
B.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
C.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
D.
associatedMusicAudience
Indicates a relationship where a piece of music, musical work, or performance is intended for, targeted at, or commonly associated with a particular audience or listener group.
-
E.
locationOfAudience
chosen
Indicates the place or setting where the audience is situated or gathered.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a63106b48190917817ec40d21a49 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.