Triple
T13748131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenny G Live |
E330269
|
entity |
| Predicate | recordingMode |
P110820
|
FINISHED |
| Object | stereo |
—
|
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: stereo | Statement: [Kenny G Live, recordingMode, stereo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingMode Context triple: [Kenny G Live, recordingMode, stereo]
-
A.
recordingMethod
Indicates the technique or process used to capture or record something (such as data, audio, or video).
-
B.
recordingState
Indicates the current status or condition of an ongoing or potential recording (e.g., whether recording is active, paused, or stopped) between entities.
-
C.
recordingType
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
D.
recordingStyle
Indicates the manner or technique used to capture or document something, such as audio, video, or data.
-
E.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
- F. None of above. chosen
Provenance (4 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:08 p.m.