Triple
T12832989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 八坂神社 |
E306833
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | 四条通 |
E1004753
|
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: [八坂神社, locatedNear, 四条通]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 四条通 Context triple: [八坂神社, locatedNear, 四条通]
-
A.
四条通
chosen
四条通 is one of Kyoto’s main east–west avenues, known for running through the central downtown area and the famous Gion district.
-
B.
半蔵門
半蔵門は、東京都千代田区に位置する皇居の西側に設けられた門で、江戸城時代からの歴史を持つ重要な出入口です。
-
C.
Meguro–Hiyoshi corridor
The Meguro–Hiyoshi corridor is a key suburban rail corridor in the Tokyo–Yokohama area linking central Tokyo with the Hiyoshi district via multiple interconnected Tokyu railway lines.
-
D.
Aoyama-dori
Aoyama-dori is a major thoroughfare in Tokyo’s Aoyama district, known for its upscale boutiques, modern architecture, and cultural landmarks.
-
E.
Shibuya–Chuo-Rinkan corridor
The Shibuya–Chuo-Rinkan corridor is a major commuter rail corridor in the Tokyo metropolitan area linking central Shibuya with the suburban Chuo-Rinkan district.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96fb0bb208190bdc4d3dc7909be06 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9bb0b48190ba3f9f92d270db83 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:34 p.m.