Triple
T26195755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mean Old Frisco |
E655095
|
entity |
| Predicate | recordLabelForCover |
P168051
|
FINISHED |
| Object | RSO Records |
—
|
NE NERFINISHED |
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: RSO Records | Statement: [Mean Old Frisco, recordLabelForCover, RSO Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelForCover Context triple: [Mean Old Frisco, recordLabelForCover, RSO Records]
-
A.
recordLabelForSingle
Indicates that a record label is responsible for producing, releasing, or distributing a particular single.
-
B.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
C.
recordLabelImprint
Indicates that one record label functions as an imprint (a subsidiary or brand) of another record label.
-
D.
recordLabelAssociated
Indicates that one entity (typically an artist or release) is or has been signed to, released under, or otherwise officially affiliated with a particular record label.
-
E.
recordLabelForNotableRecording
Indicates that a record label is responsible for producing, releasing, or prominently associated with a particular notable recording.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 26, 2026, 8:46 p.m.