Triple
T2700908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Masterworks |
E59224
|
entity |
| Predicate | catalogType |
P24430
|
FINISHED |
| Object | orchestral catalog |
—
|
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: orchestral catalog | Statement: [Columbia Masterworks, catalogType, orchestral catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogType Context triple: [Columbia Masterworks, catalogType, orchestral catalog]
-
A.
catalogueType
chosen
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
subjectOfCatalog
Indicates that something is the primary focus or entry described within a catalog or cataloging record.
-
D.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda4c8d34819094f5e4cbc5a4bb9b |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.