Triple
T3991050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priority Mail Cubic |
E86989
|
entity |
| Predicate | rateStructure |
P32811
|
FINISHED |
| Object | cubic tier system |
—
|
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: cubic tier system | Statement: [Priority Mail Cubic, rateStructure, cubic tier system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateStructure Context triple: [Priority Mail Cubic, rateStructure, cubic tier system]
-
A.
fareStructure
chosen
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
B.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
-
C.
fareStructureFeature
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
-
D.
paymentStructure
Indicates how payments are organized, scheduled, and divided between the involved parties.
-
E.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.