Triple
T22533353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東京都港区 |
E557098
|
entity |
| Predicate | containsDistrict |
P22582
|
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: [東京都港区, containsDistrict, 新橋]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 新橋 Context triple: [東京都港区, containsDistrict, 新橋]
-
A.
新橋
chosen
新橋 is a bustling business and entertainment district in central Tokyo known for its salaryman culture, izakaya alleys, and major railway hub.
-
B.
新橋駅
新橋駅は、東京都港区に位置し、JR線・地下鉄・私鉄が乗り入れる東京有数のターミナル駅で、ビジネス街や官庁街への玄関口として知られている交通拠点です。
-
C.
生口橋
生口橋 is a cable-stayed road bridge in Japan that forms part of the Shimanami Kaidō route connecting the islands of Honshu and Shikoku.
-
D.
五条大橋
五条大橋 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.
-
E.
Nijūbashi Bridge
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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed88cf08190ae7e5b6bf9a80372 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 16, 2026, 8:51 p.m.