Triple
T7927225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Thang |
E184095
|
entity |
| Predicate | singleChartSuccess |
P60345
|
FINISHED |
| Object | multiple singles reached top 10 on US Hot R&B/Hip-Hop Songs |
—
|
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: multiple singles reached top 10 on US Hot R&B/Hip-Hop Songs | Statement: [Miss Thang, singleChartSuccess, multiple singles reached top 10 on US Hot R&B/Hip-Hop Songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleChartSuccess Context triple: [Miss Thang, singleChartSuccess, multiple singles reached top 10 on US Hot R&B/Hip-Hop Songs]
-
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.
chartingSingle
chosen
Indicates that an entity appears on a music chart as a single track release.
-
C.
regionOfChartSuccess
Indicates the geographic area or market in which an entity achieved chart success.
-
D.
reissueChartSuccess
Indicates that the process of reissuing a chart has completed successfully.
-
E.
chartName
Indicates the specific title or label assigned to a chart that identifies or describes it.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aafdb5c8190b7f2ce5349305f78 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.