Triple
T12259185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOBO Award for Best African Act |
E292175
|
entity |
| Predicate | hasAwardedField |
P36199
|
FINISHED |
| Object | recorded music |
—
|
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: recorded music | Statement: [MOBO Award for Best African Act, hasAwardedField, recorded music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardedField Context triple: [MOBO Award for Best African Act, hasAwardedField, recorded music]
-
A.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
B.
isAwardedWithin
Indicates that an award or recognition is granted to an entity within a specified context, scope, or time frame.
-
C.
hasAwardedFieldOfWork
chosen
Indicates that an entity has received an award specifically for work or contributions in a particular field or area of activity.
-
D.
hasAwardUnit
Indicates that an award is associated with, measured in, or granted in terms of a specific unit (such as a quantity, category, or subdivision).
-
E.
hasAwardConnection
Indicates a relationship where an entity is connected to an award, such as by receiving, being nominated for, or otherwise associated with that award.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.