Triple
T19925440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JD.com |
E478909
|
entity |
| Predicate | listedOnStockExchange |
P524
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [JD.com, listedOnStockExchange, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedOnStockExchange Context triple: [JD.com, listedOnStockExchange, 2014]
-
A.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
B.
hasStockExchange
chosen
Indicates that an entity is associated with or listed on a particular stock exchange.
-
C.
usedByStockExchange
Indicates that something (such as a system, standard, or instrument) is utilized or adopted by a stock exchange in its operations or services.
-
D.
governsStockExchangeListedOn
Indicates that one entity has regulatory or administrative authority over the stock exchange on which another entity is listed.
-
E.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c992fc8190bd262d528be0e636 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.