Triple
T3782087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Symphony Orchestra |
E85441
|
entity |
| Predicate | recordLabelAssociation |
P34323
|
FINISHED |
| Object | major classical record labels |
—
|
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: major classical record labels | Statement: [Detroit Symphony Orchestra, recordLabelAssociation, major classical record labels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelAssociation Context triple: [Detroit Symphony Orchestra, recordLabelAssociation, major classical record labels]
-
A.
recordLabelForSingle
Indicates that a record label is responsible for producing, releasing, or distributing a particular single.
-
B.
hasRecordLabel
chosen
Indicates that an entity (typically a musical artist or release) is associated with or signed to a particular record label.
-
C.
recordLabelLocation
Indicates the geographic place where a record label is based or operates from.
-
D.
recordLabelImprint
Indicates that one record label functions as an imprint (a subsidiary or brand) of another record label.
-
E.
albumLabel
Indicates the record label or company that released or distributed a particular music album.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.