Triple
T28909277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona |
E733171
|
entity |
| Predicate | hitSingleChartRegion |
P64808
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [Corona, hitSingleChartRegion, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hitSingleChartRegion Context triple: [Corona, hitSingleChartRegion, Europe]
-
A.
hasHitSingleOnChart
Indicates that an entity (such as an artist or song) has achieved at least one single that appeared on a specified music chart.
-
B.
chartingSongInCountry
Indicates that a song appears on an official music chart within a specified country.
-
C.
chartPeakCountry
Indicates the country in which a work (such as a song or album) reached its highest position on a music chart.
-
D.
hasHitSingleInCountry
Indicates that an entity (typically a musical artist or song) has achieved at least one hit single in a specified country.
-
E.
hasInternationalHitSingle
chosen
Indicates that an entity (typically a musical artist or group) has released at least one single that achieved notable popularity or chart success in multiple countries.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65adcd92481909cbd80dd57623e82 |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:10 a.m.