Triple
T8178412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inDrive |
E190997
|
entity |
| Predicate | appFunctionality |
P40816
|
FINISHED |
| Object | real-time ride requests |
—
|
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: real-time ride requests | Statement: [inDrive, appFunctionality, real-time ride requests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appFunctionality Context triple: [inDrive, appFunctionality, real-time ride requests]
-
A.
providesFunctionalityOf
chosen
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
B.
applicationRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
C.
featuresService
Indicates that one entity provides, includes, or offers a particular service as a notable characteristic or component.
-
D.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
E.
programUse
Indicates that one entity uses, employs, or makes use of a particular program or software application.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4abb66bc81908d758c7af2e23ac6 |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.