Triple
T6824986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyocera |
E156991
|
entity |
| Predicate | stockIndex |
P10508
|
FINISHED |
| Object | Nikkei 225 |
E186734
|
NE 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: Nikkei 225 | Statement: [Kyocera, stockIndex, Nikkei 225]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nikkei 225 Context triple: [Kyocera, stockIndex, Nikkei 225]
-
A.
Nikkei 225
chosen
The Nikkei 225 is Japan’s leading stock market index, tracking 225 major blue-chip companies listed on the Tokyo Stock Exchange.
-
B.
Nifty 50
Nifty 50 is a benchmark Indian stock market index comprising 50 major companies listed on the National Stock Exchange, widely used to gauge the performance of the country’s equity market.
-
C.
JPX-Nikkei 400
JPX-Nikkei 400 is a Japanese stock market index composed of companies selected for their high profitability, capital efficiency, and investor-focused management practices.
-
D.
Nikkei
Nikkei are people of Japanese descent living outside Japan, particularly in the Americas and other parts of the Japanese diaspora.
-
E.
TOPIX
TOPIX is a major Japanese stock market index that tracks all domestic common stocks listed on the Tokyo Stock Exchange's Prime Market.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d581ea5881908ba78c6bf1ce58ee |
completed | March 27, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c723f12a148190adbb05782a2041b6 |
completed | March 28, 2026, 12:42 a.m. |
Created at: March 27, 2026, 2:18 p.m.