Triple
T31317426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Jingle Ball Tour |
E798632
|
entity |
| Predicate | associatedRadioNetwork |
P207406
|
FINISHED |
| Object | iHeartRadio |
E171150
|
NE 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: iHeartRadio | Statement: [2017 Jingle Ball Tour, associatedRadioNetwork, iHeartRadio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRadioNetwork Context triple: [2017 Jingle Ball Tour, associatedRadioNetwork, iHeartRadio]
-
A.
originalRadioNetwork
Indicates that one entity is the initial or primary radio network from which another entity originates or is derived.
-
B.
laterNetworkOfBroadcast
Indicates that one broadcast network succeeds or replaces another in time, coming into operation after the earlier network.
-
C.
radioPartnerUnitedStates
Indicates that one entity is a radio partner associated with or operating in the United States.
-
D.
countryNetwork
Indicates a relationship where countries are connected or associated through some form of shared system, collaboration, or interaction.
-
E.
televisionNetworkAssociation
Indicates a relationship where an entity is affiliated with, carried by, or part of a particular television network.
- F. None of above. chosen
Provenance (5 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ad2280c4081908706404a39c1d8bb |
completed | June 11, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:15 p.m.