Triple
T14997329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 久米邦武 |
E373991
|
entity |
| Predicate | birthPlace |
P1
|
FINISHED |
| Object | 肥前国佐賀藩 |
E575181
|
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: 肥前国佐賀藩 | Statement: [久米邦武, birthPlace, 肥前国佐賀藩]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 肥前国佐賀藩 Context triple: [久米邦武, birthPlace, 肥前国佐賀藩]
-
A.
佐賀城
佐賀城は、佐賀県佐賀市に位置し、江戸時代に肥前佐賀藩の政治・軍事の中心として機能した日本の平城です。
-
B.
土佐国
土佐国 was a former province of Japan located in present-day Kōchi Prefecture on the island of Shikoku.
-
C.
豊後大野市
豊後大野市は、大分県南部に位置し、豊かな自然景観や農業を特色とする市です。
-
D.
Hizen Domain
chosen
Hizen Domain was a powerful feudal domain in early modern Japan, centered in present-day Saga and Nagasaki Prefectures, that played a key role in the late Tokugawa period and the Meiji Restoration.
-
E.
Daimyō, Fukuoka
Daimyō, Fukuoka is a fashionable downtown district in Fukuoka City known for its trendy boutiques, cafes, and nightlife.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe969c3ba88190899f06b185e94ccf |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 10, 2026, 2:54 a.m.