Triple
T8186655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalian |
E191200
|
entity |
| Predicate | sisterCity |
P1072
|
FINISHED |
| Object | Kobe |
E499546
|
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: Kobe | Statement: [Dalian, sisterCity, Kobe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kobe Context triple: [Dalian, sisterCity, Kobe]
-
A.
Kobe
Kobe is a major port city in Japan’s Kansai region, known for its scenic harbor setting, cosmopolitan atmosphere, and famous Kobe beef.
-
B.
Kobe Nankinmachi
Kobe Nankinmachi is a famous Chinatown district in Kobe, Japan, known for its Chinese restaurants, shops, and vibrant cultural festivals.
-
C.
Kobe – Naha
Kobe – Naha is a domestic air route in Japan connecting Kobe in Hyōgo Prefecture with Naha in Okinawa Prefecture.
-
D.
Kobe, Hyogo, Japan
chosen
Kobe, Hyogo, Japan is a major port city in western Japan known for its international trade, scenic harbor setting between mountains and sea, and famous Kobe beef.
-
E.
Kobe waterfront redevelopment area
The Kobe waterfront redevelopment area is a revitalized coastal district in Kobe, Japan, featuring parks, cultural attractions, and commercial facilities that showcase the city’s modern harborfront.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4d9e01208190842170abf62d9afb |
completed | March 31, 2026, 4:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cced7a109c819092d43d9e3cfc0706 |
completed | April 1, 2026, 10:03 a.m. |
Created at: March 30, 2026, 5:41 p.m.