Triple
T1279072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Bay |
E27281
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Port of Yokohama |
E10676
|
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: Port of Yokohama | Statement: [Tokyo Bay, hasPort, Port of Yokohama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port of Yokohama Context triple: [Tokyo Bay, hasPort, Port of Yokohama]
-
A.
Port of Kobe
The Port of Kobe is one of Japan’s major international seaports, serving as a key hub for container shipping and maritime trade in the Kansai region.
-
B.
Port of Tokyo
The Port of Tokyo is one of Japan’s major international seaports, serving as a key hub for container shipping, trade, and logistics in the Greater Tokyo metropolitan area.
-
C.
Port of Nagoya
The Port of Nagoya is Japan’s busiest and largest trading port, serving as a major hub for automobile exports and international maritime commerce.
-
D.
Port of Osaka
The Port of Osaka is a major Japanese seaport and logistics hub serving the Kansai region, handling international trade, passenger ferries, and cruise ships.
-
E.
Yokohama
chosen
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_69acce5dac54819097ff1fe72a19380d |
completed | March 8, 2026, 1:18 a.m. |
Created at: March 1, 2026, 7:50 p.m.