Triple
T8577445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vertigo Records |
E203082
|
entity |
| Predicate | catalogueFeature |
P70931
|
FINISHED |
| Object | Vertigo swirl label design |
—
|
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: Vertigo swirl label design | Statement: [Vertigo Records, catalogueFeature, Vertigo swirl label design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueFeature Context triple: [Vertigo Records, catalogueFeature, Vertigo swirl label design]
-
A.
catalogueEntry
Indicates that an item is recorded as an entry within a catalogue or organized listing.
-
B.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
C.
catalogueNote
Indicates that there is a descriptive or administrative note recorded about an item within a catalogue or cataloguing process.
-
D.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
E.
catalogCharacteristic
chosen
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea97787481909ebbaa45f59cbdaa |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.