Triple
T23562257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father and Son |
E579272
|
entity |
| Predicate | BoyzoneCoverChartSuccess |
P153169
|
FINISHED |
| Object | hit in the United Kingdom |
—
|
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: hit in the United Kingdom | Statement: [Father and Son, BoyzoneCoverChartSuccess, hit in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoyzoneCoverChartSuccess Context triple: [Father and Son, BoyzoneCoverChartSuccess, hit in the United Kingdom]
-
A.
dateReachedNumberOneUK
Indicates that something (typically a song, album, or similar item) has reached the number one position on the United Kingdom charts on a specific date.
-
B.
weeksAtNumberOneUK
Indicates the number of weeks an item remained at the number one position on the UK chart.
-
C.
thirdUKNumberOneSingle
Indicates that the subject entity is the third single by the artist to reach number one on the UK singles chart.
-
D.
weeksAtNo1Singles
Indicates the number of weeks a given single (song) remained at the number one position on a specified chart.
-
E.
chartPositionScottishSingles
Indicates the position that an item achieved on the Scottish Singles music chart.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af68cddc8190ab9d0b7ee1f157ed |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:23 p.m.