Triple
T3738951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Didi Chuxing |
E79652
|
entity |
| Predicate | mobileApp |
P14571
|
FINISHED |
| Object | Didi Chuxing app |
—
|
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: Didi Chuxing app | Statement: [Didi Chuxing, mobileApp, Didi Chuxing app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileApp Context triple: [Didi Chuxing, mobileApp, Didi Chuxing app]
-
A.
hasApp
chosen
Indicates that an entity possesses, provides, or is associated with a particular application.
-
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.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
-
D.
device
Indicates that one entity is a device used, controlled, or referenced by another entity in the relationship.
-
E.
isDefaultAppFor
Indicates that an application is designated as the primary or automatically chosen program for handling a specific type of content, action, or protocol.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb404b908190b6b4ee583dee3cc9 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.