Triple
T36954968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chai |
E914165
|
entity |
| Predicate | audioFocusOfWork |
P166257
|
FINISHED |
| Object | music-driven gameplay |
—
|
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: music-driven gameplay | Statement: [Chai, audioFocusOfWork, music-driven gameplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioFocusOfWork Context triple: [Chai, audioFocusOfWork, music-driven gameplay]
-
A.
audioFocus
Indicates that one entity has priority or control over audio playback or attention relative to other potential audio sources.
-
B.
soundFocus
chosen
Indicates that attention or emphasis is directed toward a particular sound or audio source.
-
C.
audioApplication
Indicates that an entity is an application whose primary function involves processing, playing, recording, or otherwise handling audio content.
-
D.
audioWorkForm
Indicates the specific form or format that an audio work takes (e.g., audiobook, podcast, radio drama).
-
E.
deviceFocus
Indicates that attention, control, or primary interaction is directed toward a particular device in 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.