Triple
T21065772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol W-653 |
E518963
|
entity |
| Predicate | catalogNumberType |
P8090
|
FINISHED |
| Object | mono LP catalog number |
—
|
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: mono LP catalog number | Statement: [Capitol W-653, catalogNumberType, mono LP catalog number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogNumberType Context triple: [Capitol W-653, catalogNumberType, mono LP catalog number]
-
A.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
B.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
C.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
D.
labelCatalogType
Indicates that an entity is assigned a specific catalog type label, defining its classification within a cataloging system.
-
E.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb3799c8190bebabb087b917321 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:44 p.m.