Triple
T14646569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JH 1580 |
E343865
|
entity |
| Predicate | workCatalogueSystem |
P69156
|
FINISHED |
| Object | JH (Jan Hulsker) numbering |
—
|
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: JH (Jan Hulsker) numbering | Statement: [JH 1580, workCatalogueSystem, JH (Jan Hulsker) numbering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCatalogueSystem Context triple: [JH 1580, workCatalogueSystem, JH (Jan Hulsker) numbering]
-
A.
workCatalogueNumberOfWork
Indicates the catalogue number assigned to a specific work within a cataloging or classification system.
-
B.
catalogueSystem
chosen
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
C.
workCatalogueScope
Indicates that a work is included within the defined scope or coverage of a particular catalogue.
-
D.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
E.
workCatalogueGrouping
Indicates a grouping relationship that associates a work with a specific catalogue or cataloguing system in which it is organized or referenced.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ebe8048190a2935d00c9cfd8be |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.