Triple
T1279084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Bay |
E27281
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Yokosuka |
E281970
|
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: Yokosuka | Statement: [Tokyo Bay, nearCity, Yokosuka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yokosuka Context triple: [Tokyo Bay, nearCity, Yokosuka]
-
A.
Yokosuka
chosen
Yokosuka is a coastal city in Kanagawa Prefecture, Japan, known for its major naval base and strategic location at the mouth of Tokyo Bay.
-
B.
Kawanishi
Kawanishi is a city in Hyōgo Prefecture, Japan, known as a residential and commuter town within the Osaka metropolitan area.
-
C.
Shizuoka
Shizuoka is a coastal city in central Japan known for its views of Mount Fuji, green tea production, and role as the capital of Shizuoka Prefecture.
-
D.
Chiba
Chiba is a major city in Japan located east of Tokyo, known as the capital of Chiba Prefecture and a key commercial and residential hub in the Greater Tokyo Area.
-
E.
Yokohama
Yokohama is Japan’s second-largest city and a major international port located just south of Tokyo.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c092eb688190bf42bbd59e4ff289 |
completed | March 1, 2026, 10:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af989077b881909eb04ffb1e252e8c |
completed | March 10, 2026, 4:05 a.m. |
Created at: March 1, 2026, 7:50 p.m.