Triple
T4104049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Household Collections Management |
E88406
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collections management unit |
C9169
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: collections management unit Context triple: [Royal Household Collections Management, instanceOf, collections management unit]
-
A.
collection of assets
A collection of assets is an organized grouping of tangible or intangible resources, such as financial instruments, physical property, or digital items, managed together for a common purpose like investment, operations, or risk management.
-
B.
canonical collection
A canonical collection is an organized set of items or elements arranged in a standard, authoritative form that uniquely represents all relevant variations or instances within a given context.
-
C.
package management system
A package management system is a tool that automates the processes of finding, installing, upgrading, configuring, and removing software packages and their dependencies in a consistent and reliable way.
-
D.
organizational unit category
chosen
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
-
E.
group of bibliographic items
A group of bibliographic items is a collection of related references or citations treated as a single unit for organization, retrieval, or analysis in a bibliographic system.
- F. None of above.
Provenance (1 batch)
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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.