Triple
T16034012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammy Award for Best Country Duo/Group Performance |
E388919
|
entity |
| Predicate | eligiblePerformerType |
P20624
|
FINISHED |
| Object | duo |
—
|
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: duo | Statement: [Grammy Award for Best Country Duo/Group Performance, eligiblePerformerType, duo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligiblePerformerType Context triple: [Grammy Award for Best Country Duo/Group Performance, eligiblePerformerType, duo]
-
A.
eligiblePerformers
Indicates that certain entities are qualified or permitted to perform in a specified event, role, or context.
-
B.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.