Triple
T22168541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Museum Reading Room |
E547858
|
entity |
| Predicate | hasCatalogueSystem |
P69156
|
FINISHED |
| Object | centralized catalogue |
—
|
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: centralized catalogue | Statement: [British Museum Reading Room, hasCatalogueSystem, centralized catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueSystem Context triple: [British Museum Reading Room, hasCatalogueSystem, centralized catalogue]
-
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.
hasCategorySystem
Indicates that an entity is associated with or organized according to a particular categorization system.
-
C.
hasCatalogueContext
Indicates that something is associated with, or occurs within, a specific catalogue-related context or framework.
-
D.
hasCatalogView
Indicates that an entity is associated with a particular way or mode of viewing or presenting a catalog.
-
E.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6642b08190980fa0c0d2bb4229 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.