Triple
T23521068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDLP Electronic Collection |
E574507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government information collection |
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 information collection Context triple: [FDLP Electronic Collection, instanceOf, government information collection]
-
A.
government information center
A government information center is a public facility or service that provides citizens with access to official information, resources, and assistance regarding government programs, services, and regulations.
-
B.
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.
-
C.
administrative body collection
An administrative body collection is an organized grouping of official entities or agencies responsible for managing, regulating, or overseeing specific governmental or institutional functions.
-
D.
intelligence collection method
An intelligence collection method is a systematic approach or technique used to gather information from various sources to support analysis, decision-making, and operations.
-
E.
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.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:08 p.m.