Triple
T3496619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammy Award for Best R&B Performance |
E73865
|
entity |
| Predicate | hasCategoryStatus |
P20501
|
FINISHED |
| Object | active Grammy category |
—
|
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: active Grammy category | Statement: [Grammy Award for Best R&B Performance, hasCategoryStatus, active Grammy category]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCategoryStatus Context triple: [Grammy Award for Best R&B Performance, hasCategoryStatus, active Grammy category]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
categoryStatus
chosen
Indicates the current state or condition assigned to a category within a given system or context.
-
C.
hasCategoryCount
Indicates the number of distinct categories associated with a given entity.
-
D.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbd16c0081908f13535f459618d1 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.