Triple
T17665448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coral Records |
E440365
|
entity |
| Predicate | musicMarketSegment |
P36203
|
FINISHED |
| Object | popular music |
—
|
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: popular music | Statement: [Coral Records, musicMarketSegment, popular music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicMarketSegment Context triple: [Coral Records, musicMarketSegment, popular music]
-
A.
musicMarket
chosen
Indicates a relationship where an entity participates in, targets, or is associated with a particular market or commercial context for music.
-
B.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
C.
musicField
Indicates a relationship where an entity is associated with a particular field, genre, or domain within music.
-
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.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea8accc8190beea0900b0614020 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:56 a.m.