Triple
T37107252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From the Age of Swing |
E918877
|
entity |
| Predicate | recordingEraEvoked |
P22765
|
FINISHED |
| Object | 1930s swing era |
—
|
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: 1930s swing era | Statement: [From the Age of Swing, recordingEraEvoked, 1930s swing era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingEraEvoked Context triple: [From the Age of Swing, recordingEraEvoked, 1930s swing era]
-
A.
recordingEra
chosen
Indicates the historical time period or era during which the recording was made.
-
B.
reRecordingEra
Indicates that one recording is a new or updated version created in a later era relative to an earlier recording.
-
C.
recordingFormatEra
Indicates the historical time period or era associated with the recording format used for an audio or video recording.
-
D.
musicalEra
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
E.
primaryEraOfRecordingsReissued
Indicates that the associated recordings being reissued predominantly originate from a particular historical or stylistic era.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:14 p.m.