Triple
T22440647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 新年一般参賀 |
E554745
|
entity |
| Predicate | relatedPlace |
P3158
|
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: [新年一般参賀, relatedPlace, 二重橋]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 二重橋 Context triple: [新年一般参賀, relatedPlace, 二重橋]
-
A.
宇治橋
宇治橋 is a historic bridge in Uji, Kyoto Prefecture, renowned as one of Japan’s oldest bridges and a prominent landmark appearing in classical literature and scenic views over the Uji River.
-
B.
長堀橋
長堀橋は、大阪市中央区に位置し、地下鉄駅やビジネス街・繁華街が集まる市内有数の交通・商業拠点エリアである。
-
C.
五条大橋
五条大橋 is a historic bridge in Kyoto, Japan, best known as the legendary site of the encounter between the warrior monk Benkei and the folk hero Minamoto no Yoshitsune.
-
D.
半蔵門
半蔵門は、東京都千代田区に位置する皇居の西側に設けられた門で、江戸城時代からの歴史を持つ重要な出入口です。
-
E.
Nijūbashi Bridge
chosen
Nijūbashi Bridge is a famous pair of arched bridges at the main entrance to Tokyo’s Imperial Palace, known as one of Japan’s most iconic and photographed landmarks.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
Created at: April 16, 2026, 8:47 p.m.