Triple
T7935575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John W. Wydler Government Documents Depository at Hofstra University |
E184280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government documents depository |
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 documents depository Context triple: [John W. Wydler Government Documents Depository at Hofstra University, instanceOf, government documents depository]
-
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.
office of the United States government
An office of the United States government is an official organizational unit or position within a federal branch or agency that carries out specific governmental functions, duties, and responsibilities under U.S. law.
-
C.
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.
-
D.
government building
A government building is a structure owned or used by a public authority to house offices, services, and functions related to the administration and governance of a city, region, or country.
-
E.
government post
A government post is an official position or office within a governmental organization, held by an individual responsible for carrying out specific public duties and administrative functions.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.