Triple
T33952159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucks Fizz |
E870467
|
entity |
| Predicate | numberOneSingle |
P81279
|
FINISHED |
| Object | Making Your Mind Up |
E870468
|
NE 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: Making Your Mind Up | Statement: [Bucks Fizz, numberOneSingle, Making Your Mind Up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOneSingle Context triple: [Bucks Fizz, numberOneSingle, Making Your Mind Up]
-
A.
hasNumberOneSingleIn
chosen
Indicates that an entity has achieved at least one number-one single within a specified chart, region, or context.
-
B.
digitSymbolForOne
Indicates that something is the written or symbolic representation used to denote the numeric value one.
-
C.
oneOfNine
Indicates that the subject is exactly one member of a specific group or set containing nine distinct options.
-
D.
numberOfSingles
Indicates the count of individual single items (such as single tracks, units, or occurrences) associated with a given entity.
-
E.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
- F. None of above.
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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a01e68a481909266a197c3b96354 |
completed | June 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.