Triple
T28488280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Don’t Talk Anymore |
E720892
|
entity |
| Predicate | reachedTopTenIn |
P70530
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [We Don’t Talk Anymore, reachedTopTenIn, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedTopTenIn Context triple: [We Don’t Talk Anymore, reachedTopTenIn, Australia]
-
A.
peakedWithinTopTenOn
Indicates that something (such as a work, product, or performance) reached a highest ranking position within the top ten on a specified chart, list, or ranking system.
-
B.
enteredChartTop10
chosen
Indicates that something has achieved a position within the top 10 of a ranked chart or listing.
-
C.
numberOfTop10SinglesUS
Indicates the number of singles by an entity that have reached the top 10 positions on music charts in the United States.
-
D.
achievedPopularityIn
Indicates that an entity became popular or widely recognized within a specified place, group, or context.
-
E.
debutedAtNumberOneOn
Indicates that an item (such as a song, album, or work) entered a ranked chart for the first time directly in the top (number one) position.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f12a81081909ddd3b1ffc2deba6 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:59 a.m.