Triple
T31895943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber driver-partners |
E814282
|
entity |
| Predicate | paysFeeTo |
P109497
|
FINISHED |
| Object | Uber |
—
|
NE NERFINISHED |
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: Uber | Statement: [Uber driver-partners, paysFeeTo, Uber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paysFeeTo Context triple: [Uber driver-partners, paysFeeTo, Uber]
-
A.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
B.
chargesFeeFor
chosen
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
C.
feePaidIn
Indicates that a specified fee has been paid in a particular currency or payment medium.
-
D.
chargesMembershipFee
Indicates that an entity requires another entity to pay a membership fee in order to access its services, benefits, or participation.
-
E.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b1647918819085ec718e13f9926a |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:58 p.m.