Triple
T15832306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuaidi Dache |
E383900
|
entity |
| Predicate | marketPositionBeforeMerger |
P119813
|
FINISHED |
| Object | major ride-hailing platform in China |
—
|
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: major ride-hailing platform in China | Statement: [Kuaidi Dache, marketPositionBeforeMerger, major ride-hailing platform in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketPositionBeforeMerger Context triple: [Kuaidi Dache, marketPositionBeforeMerger, major ride-hailing platform in China]
-
A.
governingBodyBeforeMerger
Indicates that one entity functioned as the governing body of another entity prior to a merger event.
-
B.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
C.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
D.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
E.
parentCompanyAfterMerger
Indicates that one company is the resulting parent company of another following a merger.
- F. None of above. chosen
Provenance (4 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e653e388190a4696cdb22546715 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.