Triple
T1653358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Stock Exchange |
E35742
|
entity |
| Predicate | tradingSystemType |
P12491
|
FINISHED |
| Object | electronic trading system |
—
|
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: electronic trading system | Statement: [Tokyo Stock Exchange, tradingSystemType, electronic trading system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingSystemType Context triple: [Tokyo Stock Exchange, tradingSystemType, electronic trading system]
-
A.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
B.
hasTradingModel
Indicates that one entity uses, is governed by, or is associated with a particular trading model.
-
C.
hasElectronicTradingSystem
chosen
Indicates that an entity operates or utilizes an electronic system for executing trades or transactions.
-
D.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
-
E.
electronicTradingPlatform
Indicates a relationship where financial instruments are bought and sold through an electronic trading system or marketplace rather than via traditional manual or floor-based methods.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.