Triple
T30235162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin Billboard Music Award for Vocal Duet or Collaboration of the Year |
E768744
|
entity |
| Predicate | minimumPerformers |
P84129
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Latin Billboard Music Award for Vocal Duet or Collaboration of the Year, minimumPerformers, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumPerformers Context triple: [Latin Billboard Music Award for Vocal Duet or Collaboration of the Year, minimumPerformers, 2]
-
A.
numberOfPerformers
chosen
Indicates the quantity of performers involved in a given event, act, or performance.
-
B.
approximateNumberOfPerformers
Indicates an estimated count of performers involved in an event or performance.
-
C.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
-
D.
eligiblePerformers
Indicates that certain entities are qualified or permitted to perform in a specified event, role, or context.
-
E.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 7:37 p.m.