Triple
T32762175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realsongs |
E837783
|
entity |
| Predicate | hasPrimaryGenreScope |
P51264
|
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: [Realsongs, hasPrimaryGenreScope, popular music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGenreScope Context triple: [Realsongs, hasPrimaryGenreScope, popular music]
-
A.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
B.
hasMainGenre
chosen
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
C.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
D.
hasPrimaryGenreRegion
Indicates that an entity’s main or dominant genre is associated with a particular geographic region.
-
E.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: May 1, 2026, 1:13 a.m.