Triple
T36056845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States Greffe archives of Jersey |
E1042968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government records repository |
C47365
|
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 records repository Context triple: [States Greffe archives of Jersey, instanceOf, government records repository]
-
A.
government document collection
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.
intergovernmental organization records
Intergovernmental organization records are documented materials produced, received, or maintained by organizations formed by sovereign states to facilitate cooperation, coordination, and decision-making on international or regional issues.
-
C.
public records repository
chosen
A public records repository is a centralized system or facility for collecting, preserving, organizing, and providing public access to official documents and information generated or held by government or public institutions.
-
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.
archival office
An archival office is an organizational unit responsible for systematically collecting, preserving, organizing, and providing access to records and documents of long-term administrative, 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:08 p.m.