Triple
T11284586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Commissary Agency |
E267152
|
entity |
| Predicate | pricingPolicy |
P8244
|
FINISHED |
| Object | sells at cost plus a small surcharge |
—
|
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: sells at cost plus a small surcharge | Statement: [Defense Commissary Agency, pricingPolicy, sells at cost plus a small surcharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pricingPolicy Context triple: [Defense Commissary Agency, pricingPolicy, sells at cost plus a small surcharge]
-
A.
pricingStrategy
chosen
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
B.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
C.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
D.
ticketPricePolicy
Indicates the pricing rules or conditions that determine how much a ticket costs in a given context.
-
E.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9855e8881909bd301718cbd8ca1 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.