Triple
T4692578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon’s royal archives |
E104068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government record repository |
C5303
|
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: government record repository Context triple: [Lisbon’s royal archives, instanceOf, government record repository]
-
A.
government document collection
chosen
A government document collection is an organized set of official records, reports, laws, and publications produced or issued by governmental bodies, maintained for reference, accountability, and public access.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
archival record
An archival record is a preserved document or item, created or received in the course of activities, maintained as evidence of those activities and retained for its enduring informational, legal, or historical value.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.