Triple
T28049972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日本取引所グループ |
E708793
|
entity |
| Predicate | 代表的な株価指数 |
P10508
|
FINISHED |
| Object | JPX日経中小型株指数 |
—
|
NE NERFINISHED |
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: JPX日経中小型株指数 | Statement: [日本取引所グループ, 代表的な株価指数, JPX日経中小型株指数]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 代表的な株価指数 Context triple: [日本取引所グループ, 代表的な株価指数, JPX日経中小型株指数]
-
A.
stockIndex
chosen
Indicates a relationship where a stock market index tracks or represents the aggregated performance of a selected group of stocks.
-
B.
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.
-
C.
isIncludedInMajorUSIndexes
Indicates that a financial instrument is a constituent of one or more major U.S. stock market indexes (such as the S&P 500, Dow Jones Industrial Average, or Nasdaq-100).
-
D.
isPriceIndex
Indicates that a value represents a price index, expressing the relative level or change of prices compared to a reference point or period.
-
E.
stocks
Indicates that one entity keeps or maintains a supply of another entity available for use or sale.
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:32 p.m.