Triple
T22130359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Unforgiven |
E546888
|
entity |
| Predicate | europeanAirplay |
P147112
|
FINISHED |
| Object | significant |
—
|
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: significant | Statement: [The Unforgiven, europeanAirplay, significant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: europeanAirplay Context triple: [The Unforgiven, europeanAirplay, significant]
-
A.
EuropeChartPerformance
Indicates how well something ranks or performs on music or sales charts specifically within European markets.
-
B.
chartPositionEuropeanHot100
Indicates the position an item reached on the European Hot 100 music chart.
-
C.
adoptedAsEUanthemBy
Indicates that a piece of music or song has been officially adopted as the anthem by the European Union.
-
D.
hasApproximateEuropeanFrequency
Indicates that the subject has an estimated or approximate occurrence rate within European populations.
-
E.
rankingInEurope
Indicates the position or level an entity holds within a comparative ranking limited to Europe.
- F. None of above. chosen
Provenance (4 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129851db8819082d50bbb73670bf6 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.