Triple
T33739355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loads-a-Money |
E864516
|
entity |
| Predicate | songChartPerformance |
P87648
|
FINISHED |
| Object | UK Singles Chart hit |
—
|
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: UK Singles Chart hit | Statement: [Loads-a-Money, songChartPerformance, UK Singles Chart hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songChartPerformance Context triple: [Loads-a-Money, songChartPerformance, UK Singles Chart hit]
-
A.
chartingSongInCountry
chosen
Indicates that a song appears on an official music chart within a specified country.
-
B.
chartPeakPublication
Indicates the publication (such as a chart or listing) in which an item achieved its highest chart position.
-
C.
chartPositionARIALatinPopAirplay
Indicates the position something holds on the ARIA Latin Pop Airplay music chart.
-
D.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
E.
notableSingleChartPerformance
Indicates that an entity achieved a particularly significant or distinguished performance on a music singles chart.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb5698748190bd5e79c36a615b91 |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.