Triple
T13105420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBO.gov |
E310830
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government procurement website |
C17763
|
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 website Context triple: [FBO.gov, instanceOf, government procurement website]
-
A.
government procurement agreement
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.
-
B.
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.
-
C.
procurement agency
A procurement agency is an organization that manages the sourcing, negotiation, and acquisition of goods and services on behalf of a client or institution to ensure cost-effective and compliant purchasing.
-
D.
procurement policy office
The procurement policy office is responsible for developing, implementing, and overseeing rules, guidelines, and standards that govern how an organization acquires goods and services to ensure fairness, compliance, and value for money.
-
E.
web-based procurement application
chosen
A web-based procurement application is an online system that streamlines and manages the end-to-end purchasing process, from requisition and supplier selection to order placement, approval workflows, and tracking.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:05 p.m.