Triple
T31049530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown |
E791219
|
entity |
| Predicate | mainSingleChartSuccess |
P127099
|
FINISHED |
| Object | Downtown (song) |
—
|
NE NERFINISHED |
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: Downtown (song) | Statement: [Downtown, mainSingleChartSuccess, Downtown (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSingleChartSuccess Context triple: [Downtown, mainSingleChartSuccess, Downtown (song)]
-
A.
chartingSingle
Indicates that an entity appears on a music chart as a single track release.
-
B.
hasChartSuccessWith
chosen
Indicates that an entity has achieved measurable success on music or performance charts in connection with another specified entity.
-
C.
chartSuccessWith
Indicates a relationship where one entity measures, tracks, or visualizes the success or performance of another entity using charts or similar representations.
-
D.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
E.
chartSuccessVersion
Indicates that a particular version of something has successfully appeared on or performed well in a chart or ranking.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9 p.m.