Triple
T1226159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Voice UK |
E26330
|
entity |
| Predicate | hasPrize |
P14849
|
FINISHED |
| Object | recording contract |
—
|
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: recording contract | Statement: [The Voice UK, hasPrize, recording contract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrize Context triple: [The Voice UK, hasPrize, recording contract]
-
A.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
B.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
C.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
D.
winnerReceives
chosen
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
E.
hasTrophyForm
Indicates that one entity exists in, or is characterized by, a special trophy-like form or version of another entity.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be39908481908cca21aaf0828415 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.