Triple
T21685139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 米騒動 |
E535209
|
entity |
| Predicate | 場所 |
P16368
|
FINISHED |
| Object | 東京府 |
—
|
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: 東京府 | Statement: [米騒動, 場所, 東京府]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 東京府 Context triple: [米騒動, 場所, 東京府]
-
A.
Tokyo Prefecture
chosen
Tokyo Prefecture is Japan’s capital metropolitan region, encompassing the city of Tokyo and serving as the country’s political, economic, and cultural center.
-
B.
Bunkyō City
Bunkyō City is a special ward in central Tokyo, Japan, known for its universities, historic temples, and quiet residential neighborhoods.
-
C.
Chiba
Chiba is a major city in Japan located east of Tokyo, known as the capital of Chiba Prefecture and a key commercial and residential hub in the Greater Tokyo Area.
-
D.
Kyoto Prefecture
Kyoto Prefecture is a region in Japan’s Kansai area known for its historic capital city of Kyoto, famous temples, traditional culture, and well-preserved heritage sites.
-
E.
Osaka Prefecture
Osaka Prefecture is a populous and economically vital region in Japan’s Kansai area, centered on the city of Osaka and known as a major hub of commerce, industry, and culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
Created at: April 16, 2026, 6:44 p.m.