Triple
T19750751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alibaba Group Holding Limited |
E474364
|
entity |
| Predicate | alsoServesMarket |
P2714
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Alibaba Group Holding Limited, alsoServesMarket, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoServesMarket Context triple: [Alibaba Group Holding Limited, alsoServesMarket, global]
-
A.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
B.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
C.
hasMarket
chosen
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
D.
relatedMarket
Indicates that two markets are connected or associated, such that activity, conditions, or changes in one market are relevant to or influence the other.
-
E.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529875688190952af476aa5be492 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.