Triple
T26136422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grab Holdings Inc. |
E659394
|
entity |
| Predicate | acquiredBusiness |
P16131
|
FINISHED |
| Object | Uber Southeast Asia operations |
—
|
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: Uber Southeast Asia operations | Statement: [Grab Holdings Inc., acquiredBusiness, Uber Southeast Asia operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredBusiness Context triple: [Grab Holdings Inc., acquiredBusiness, Uber Southeast Asia operations]
-
A.
acquiredCompany
chosen
Indicates that one entity has purchased and taken ownership or control of another company.
-
B.
underlyingCompanyAcquisition
Indicates that one company is the target or subject of an acquisition by another company.
-
C.
acquisition
Indicates the act or relationship in which one entity obtains ownership or control of another entity, asset, or resource.
-
D.
acquiredCompanyType
Indicates the classification or category of the company that was acquired in an acquisition relationship.
-
E.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b97942c8190b3d913dcdcd30e08 |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:17 p.m.