Triple
T28049945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日本取引所グループ |
E708793
|
entity |
| Predicate | 上場市場 |
P6939
|
FINISHED |
| Object | 東京証券取引所プライム市場 |
—
|
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: 東京証券取引所プライム市場 | Statement: [日本取引所グループ, 上場市場, 東京証券取引所プライム市場]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 上場市場 Context triple: [日本取引所グループ, 上場市場, 東京証券取引所プライム市場]
-
A.
mainStockExchangeOf
Indicates that one entity serves as the primary stock exchange on which the other entity (typically a company or financial instrument) is chiefly listed or traded.
-
B.
isPrimarySecuritiesMarketOf
Indicates that a market serves as the main or principal venue where a particular entity’s securities are initially issued, listed, or predominantly traded.
-
C.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
D.
stockExchangeContext
Indicates a relationship or action occurring within the context of a stock exchange, such as trading, listing, or pricing of financial instruments.
-
E.
isOneOfLargestStockExchangesIn
Indicates that an entity ranks among the largest stock exchanges within a specified country or region.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd88d408190af30ebec8469b050 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:32 p.m.