Triple
T22760435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL (mono LP series) |
E562970
|
entity |
| Predicate | catalogSystem |
P69156
|
FINISHED |
| Object | Kapp Records KL/KS numbering system |
—
|
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: Kapp Records KL/KS numbering system | Statement: [KL (mono LP series), catalogSystem, Kapp Records KL/KS numbering system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogSystem Context triple: [KL (mono LP series), catalogSystem, Kapp Records KL/KS numbering system]
-
A.
catalogueSystem
chosen
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
B.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
controlsCatalogOf
Indicates that one entity has authority over or manages the catalog or collection belonging to another entity.
-
D.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
E.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7c45b881908b29ba1439038789 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:26 p.m.