Triple
T21904500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USRA Final System Plan reports |
E540898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government planning document series |
C19344
|
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 planning document series Context triple: [USRA Final System Plan reports, instanceOf, government planning document series]
-
A.
government strategy document
chosen
A government strategy document is an official, forward-looking plan that outlines a public authority’s long-term goals, priorities, and coordinated actions for addressing specific policy areas or national challenges.
-
B.
advisory document series
An advisory document series is a recurring collection of written guidance materials that provide expert recommendations, best practices, and updates on a specific topic or domain over time.
-
C.
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.
-
D.
government-sponsored documentation project
A government-sponsored documentation project is an officially funded and managed initiative to systematically collect, record, and preserve information, data, or cultural materials for public, administrative, or historical purposes.
-
E.
United Nations document series
A United Nations document series is a categorized collection of official UN documents grouped under a common symbol or theme to organize and track related records over time.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:29 p.m.