Triple
T35406825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governmentwide Acquisition Contracts |
E1023381
|
entity |
| Predicate | vendorStatus |
P63501
|
FINISHED |
| Object | pre‑vetted vendors |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: pre‑vetted vendors | Statement: [Governmentwide Acquisition Contracts, vendorStatus, pre‑vetted vendors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorStatus Context triple: [Governmentwide Acquisition Contracts, vendorStatus, pre‑vetted vendors]
-
A.
vendorSupportStatus
Indicates the current level or state of support provided by a vendor for a product, service, or customer.
-
B.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
C.
manufacturerStatus
Indicates the current operational or business condition of a manufacturer in relation to the product or agreement in question.
-
D.
eligibleVendors
chosen
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
-
E.
supplyStatus
Indicates the current availability or condition of a required supply in relation to a given entity or context.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.