Triple
T15392394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長堀鶴見緑地線 |
E368079
|
entity |
| Predicate | 主要経由地 |
P65699
|
FINISHED |
| Object |
長堀橋
長堀橋は、大阪市中央区に位置し、地下鉄駅やビジネス街・繁華街が集まる市内有数の交通・商業拠点エリアである。
|
E1155369
|
NE FINISHED |
How this triple was built (4 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.
五条大橋
五条大橋 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.
-
B.
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.
-
C.
Nihonbashi Bridge
Nihonbashi Bridge is a historic stone arch bridge in central Tokyo that has long served as Japan’s traditional kilometer zero and a key commercial and cultural landmark.
-
D.
Gobyobashi Bridge
Gobyobashi Bridge is a small, historic bridge within Koyasan’s Okunoin cemetery complex in Japan, crossed by pilgrims on their way to the mausoleum of Kobo Daishi.
-
E.
Sakurabashi Bridge
Sakurabashi Bridge is a distinctive pedestrian bridge in Tokyo known for its unique X-shaped design spanning the Sumida River and connecting popular riverside parks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 長堀橋 Triple: [長堀鶴見緑地線, 主要経由地, 長堀橋]
Generated description
長堀橋は、大阪市中央区に位置し、地下鉄駅やビジネス街・繁華街が集まる市内有数の交通・商業拠点エリアである。
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 長堀橋 Target entity description: 長堀橋は、大阪市中央区に位置し、地下鉄駅やビジネス街・繁華街が集まる市内有数の交通・商業拠点エリアである。
-
A.
五条大橋
五条大橋 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.
-
B.
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.
-
C.
Nihonbashi Bridge
Nihonbashi Bridge is a historic stone arch bridge in central Tokyo that has long served as Japan’s traditional kilometer zero and a key commercial and cultural landmark.
-
D.
Gobyobashi Bridge
Gobyobashi Bridge is a small, historic bridge within Koyasan’s Okunoin cemetery complex in Japan, crossed by pilgrims on their way to the mausoleum of Kobo Daishi.
-
E.
Sakurabashi Bridge
Sakurabashi Bridge is a distinctive pedestrian bridge in Tokyo known for its unique X-shaped design spanning the Sumida River and connecting popular riverside parks.
- F. None of above. chosen
Provenance (5 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1350699c8190acf7830d88455851 |
completed | May 9, 2026, 10:58 a.m. |
| NEDg | Description generation | batch_69ff17c6837c8190a2b6fa1ac9c3de01 |
completed | May 9, 2026, 11:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff184d63e88190906689e14cfc8933 |
completed | May 9, 2026, 11:19 a.m. |
Created at: April 10, 2026, 3:19 a.m.