Triple
T11637117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Register of Tartans |
E276554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national database |
C14788
|
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: national database Context triple: [Scottish Register of Tartans, instanceOf, national database]
-
A.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
B.
federal government database
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
-
C.
United States federal government database
A United States federal government database is an official, centrally managed digital repository that stores, organizes, and provides controlled access to data collected or maintained by federal agencies for governance, regulatory, research, and public transparency purposes.
-
D.
federal data repository
A federal data repository is a centralized, government-managed system for collecting, storing, and providing controlled access to official datasets for analysis, oversight, and public use.
-
E.
database
chosen
A database is an organized collection of structured or unstructured data stored and managed in a way that enables efficient retrieval, modification, and administration.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.