Triple
T21672776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Night |
E534892
|
entity |
| Predicate | originalChartSuccess |
P127099
|
FINISHED |
| Object | R&B hit |
—
|
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: R&B hit | Statement: [Black Night, originalChartSuccess, R&B hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalChartSuccess Context triple: [Black Night, originalChartSuccess, R&B hit]
-
A.
chartSuccessWith
Indicates a relationship where one entity measures, tracks, or visualizes the success or performance of another entity using charts or similar representations.
-
B.
hasChartSuccessWith
chosen
Indicates that an entity has achieved measurable success on music or performance charts in connection with another specified entity.
-
C.
chartSuccessInCountry
Indicates that something has achieved a measurable level of success on music or sales charts within a specified country.
-
D.
helpedChart
Indicates that one entity assisted in creating, developing, or planning the course or direction of another entity or initiative.
-
E.
regionOfChartSuccess
Indicates the geographic area or market in which an entity achieved chart success.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0cd7648190b9981393f0b2bee9 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:41 p.m.