Triple
T3564199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Row Records |
E75404
|
entity |
| Predicate | catalogValue |
P50388
|
FINISHED |
| Object | owns rights to classic 1990s hip hop albums |
—
|
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: owns rights to classic 1990s hip hop albums | Statement: [Death Row Records, catalogValue, owns rights to classic 1990s hip hop albums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogValue Context triple: [Death Row Records, catalogValue, owns rights to classic 1990s hip hop albums]
-
A.
catalogCode
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
B.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
-
D.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
E.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a76c008190a2056b6d990776fe |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:21 p.m.