Triple
T28921240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boom Radio |
E733516
|
entity |
| Predicate | listenerEngagement |
P65330
|
FINISHED |
| Object | phone-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: phone-ins | Statement: [Boom Radio, listenerEngagement, phone-ins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listenerEngagement Context triple: [Boom Radio, listenerEngagement, phone-ins]
-
A.
peakListenership
Indicates the time or context in which an entity (such as a program, station, or platform) reaches its highest number of listeners.
-
B.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
C.
includesEngagement
chosen
Indicates that one entity incorporates or involves another entity in an engagement, interaction, or participatory activity.
-
D.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
E.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b1b09a08190934a1b04d6381028 |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:19 a.m.