Triple
T3926189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smells Like Records |
E93281
|
entity |
| Predicate | catalogScope |
P16090
|
FINISHED |
| Object | full-length 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: full-length albums | Statement: [Smells Like Records, catalogScope, full-length albums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogScope Context triple: [Smells Like Records, catalogScope, full-length albums]
-
A.
scopeOfProducts
chosen
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
B.
promotionScope
Indicates the range or extent within which a promotion or promotional offer is valid or applicable.
-
C.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed80a1e48190aa39748b9db42701 |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.