Triple
T1000426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammy Award for Best Female Pop Vocal Performance |
E21589
|
entity |
| Predicate | performanceFormat |
P130
|
FINISHED |
| Object | recorded track |
—
|
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: recorded track | Statement: [Grammy Award for Best Female Pop Vocal Performance, performanceFormat, recorded track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceFormat Context triple: [Grammy Award for Best Female Pop Vocal Performance, performanceFormat, recorded track]
-
A.
performanceStyle
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
D.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
E.
notableFormat
Indicates that something is particularly recognized or distinguished for being in a specific format.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.