Triple
T2913968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Award Schedules Program |
E63752
|
entity |
| Predicate | procurementMethod |
P42886
|
FINISHED |
| Object | task orders and delivery orders |
—
|
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: task orders and delivery orders | Statement: [Multiple Award Schedules Program, procurementMethod, task orders and delivery orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: procurementMethod Context triple: [Multiple Award Schedules Program, procurementMethod, task orders and delivery orders]
-
A.
biddingProcessType
Indicates the specific method or procedure used to conduct a bidding or tendering process between parties.
-
B.
procurementPartner
Indicates that one entity serves as a supplier or provider responsible for acquiring goods or services on behalf of another entity.
-
C.
submissionMethod
Indicates the means or channel through which something is submitted or delivered.
-
D.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
-
E.
bidWinner
Indicates that the referenced entity is the winner of a particular bidding or auction process.
- F. None of above. chosen
Provenance (4 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ecaba48190a8e22c74a111fded |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddedd72c819094a9c4161af07780 |
completed | March 7, 2026, 8:12 a.m. |
Created at: March 6, 2026, 10:11 p.m.