Triple
T1549261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UberXL |
E33049
|
entity |
| Predicate | relativePriceLevel |
P16098
|
FINISHED |
| Object | higher than UberX |
—
|
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: higher than UberX | Statement: [UberXL, relativePriceLevel, higher than UberX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePriceLevel Context triple: [UberXL, relativePriceLevel, higher than UberX]
-
A.
relativePrice
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
B.
priceRelationship
chosen
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
C.
priceInfluencedBy
Indicates that the price of one entity is affected or determined by another specified factor or entity.
-
D.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
E.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.