Triple
T824053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PayPal Working Capital |
E17812
|
entity |
| Predicate | feeDeterminants |
P15879
|
FINISHED |
| Object | sales history |
—
|
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: sales history | Statement: [PayPal Working Capital, feeDeterminants, sales history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeDeterminants Context triple: [PayPal Working Capital, feeDeterminants, sales history]
-
A.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
B.
priceDeterminedBy
chosen
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
C.
featuresCharge
Indicates that one entity includes, offers, or is characterized by a particular charge (such as a fee, cost, or pricing component).
-
D.
fareCapping
Indicates a limit on the total amount a rider can be charged for fares over a set period, after which additional trips are free or discounted.
-
E.
fare
Indicates the price or cost required for a person or thing to be transported by a particular mode of travel or service.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7d3984819089aefbf12d3b3c2c |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.