Triple
T3132965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama Marine Tower |
E65458
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Yamashita Park |
E327891
|
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: Yamashita Park | Statement: [Yokohama Marine Tower, near, Yamashita Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamashita Park Context triple: [Yokohama Marine Tower, near, Yamashita Park]
-
A.
Yamashita Park
chosen
Yamashita Park is a famous seaside public park in Yokohama, Japan, known for its waterfront promenade, harbor views, and historic landmarks.
-
B.
Okubo Park
Okubo Park is a public urban park located in the Ōkubo district of Shinjuku, Tokyo, known as a local green space amid the dense cityscape.
-
C.
Shukugawa Park
Shukugawa Park is a scenic riverside park in Nishinomiya, Japan, renowned for its cherry blossom-lined paths and seasonal beauty.
-
D.
Maruyama Park
Maruyama Park is a famous public park in Kyoto, Japan, especially known for its cherry blossoms and traditional atmosphere.
-
E.
Higashi Ayase Park
Higashi Ayase Park is a public green space in Tokyo’s Adachi ward, known for its sports facilities, playgrounds, and walking paths.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada56104ec8190a14591ed73f3fe83 |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b261f21620819088b6e7f782efe0b8 |
completed | March 12, 2026, 6:49 a.m. |
Created at: March 8, 2026, 3:04 p.m.