Triple
T2103467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Pro |
E37140
|
entity |
| Predicate | launchContext |
P11671
|
FINISHED |
| Object | introduced to reward consistent, high-quality drivers |
—
|
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: introduced to reward consistent, high-quality drivers | Statement: [Uber Pro, launchContext, introduced to reward consistent, high-quality drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchContext Context triple: [Uber Pro, launchContext, introduced to reward consistent, high-quality drivers]
-
A.
launchLocation
Indicates the place or site from which something is launched or set into motion.
-
B.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
C.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
D.
launchProfile
Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
-
E.
launchEvent
chosen
Indicates an event in which something is formally initiated, introduced, or set into operation.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabf7cdc81909636dff34badc1c5 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.