Triple
T7223166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transportation Improvement Program |
E150310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federally required planning document |
C12268
|
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: federally required planning document Context triple: [Transportation Improvement Program, instanceOf, federally required planning document]
-
A.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
B.
regulatory document
chosen
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
-
C.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
-
D.
federal obligation
A federal obligation is a legally binding duty or commitment imposed or recognized by the national government, typically involving the payment of money, provision of services, or compliance with regulatory requirements.
-
E.
United States federal document
A United States federal document is an official record, form, publication, or communication created, issued, or maintained by a federal agency or branch of the U.S. government in the course of its authorized duties.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:54 p.m.