Triple
T4371189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billboard Adult Contemporary chart |
E98898
|
entity |
| Predicate | typicalGenresIncluded |
P55821
|
FINISHED |
| Object | soft rock |
—
|
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: soft rock | Statement: [Billboard Adult Contemporary chart, typicalGenresIncluded, soft rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGenresIncluded Context triple: [Billboard Adult Contemporary chart, typicalGenresIncluded, soft rock]
-
A.
commonGenre
Indicates that two entities share at least one genre in common.
-
B.
coveredInGenre
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
C.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
D.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
E.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
- F. None of above. chosen
Provenance (4 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521dffbc8190b9300a7f4f64bdc0 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.