Triple
T18361062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BET Award for Best Male R&B/Pop Artist |
E439914
|
entity |
| Predicate | typicalNominationBasis |
P13230
|
FINISHED |
| Object | commercial success |
—
|
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: commercial success | Statement: [BET Award for Best Male R&B/Pop Artist, typicalNominationBasis, commercial success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNominationBasis Context triple: [BET Award for Best Male R&B/Pop Artist, typicalNominationBasis, commercial success]
-
A.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
B.
votingBasis
chosen
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
C.
typicalNominees
Indicates that the specified entities are the usual or commonly selected candidates or recipients associated with something.
-
D.
nominated
Indicates that one entity formally proposes or selects another entity for a position, role, award, or recognition.
-
E.
candidateNomination
Indicates that an individual is formally put forward or proposed as a candidate for a position, role, or office.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516db045c8190b20c209225a53b9a |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.