Triple
T460418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyft |
E7323
|
entity |
| Predicate | usesPricingModel |
P8244
|
FINISHED |
| Object | dynamic pricing |
—
|
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: dynamic pricing | Statement: [Lyft, usesPricingModel, dynamic pricing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPricingModel Context triple: [Lyft, usesPricingModel, dynamic pricing]
-
A.
usesBusinessModel
Indicates that one entity operates according to, or applies in practice, the business model defined or provided by another entity.
-
B.
pricingStrategy
chosen
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
C.
usedOnMode
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
D.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
E.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbd6ed481909ec40f12b5b675c8 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.