Triple
T33651907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northbound Trading |
E862120
|
entity |
| Predicate | tradingInstruments |
P26480
|
FINISHED |
| Object | Chinese onshore bonds |
—
|
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: Chinese onshore bonds | Statement: [Northbound Trading, tradingInstruments, Chinese onshore bonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingInstruments Context triple: [Northbound Trading, tradingInstruments, Chinese onshore bonds]
-
A.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
B.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
C.
tradingMedium
Indicates that one entity serves as the medium or instrument through which another entity conducts trade or exchange.
-
D.
productsTraded
chosen
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
E.
instrumentClassification
Indicates that one entity is classified as a particular type or category of instrument in relation to another 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 1:42 a.m.