Triple
T35406719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Agreements Act |
E1023379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government procurement law |
C12135
|
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 procurement law Context triple: [Trade Agreements Act, instanceOf, government procurement law]
-
A.
government procurement framework
A government procurement framework is a structured set of laws, policies, and procedures that guide how public sector entities plan, solicit, evaluate, and award contracts for goods, services, and works to ensure transparency, fairness, and value for money.
-
B.
government procurement manual
A government procurement manual is an official guide that outlines the policies, procedures, and standards for acquiring goods, services, and works using public funds.
-
C.
government procurement agreement
chosen
A government procurement agreement is a formal arrangement that sets rules and commitments for how public authorities purchase goods, services, and works, typically to ensure transparency, fairness, and non-discrimination among suppliers.
-
D.
government procurement program
A government procurement program is a structured system through which public sector entities acquire goods, services, and works from external suppliers in accordance with defined policies, regulations, and budgetary objectives.
-
E.
government procurement registration system
A government procurement registration system is a platform that enables suppliers to register, validate eligibility, and maintain profiles for participating in public sector bidding and contracting processes.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.