Triple
T10814329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omiya Bonsai Village |
E255184
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Omiya Park |
E876434
|
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: Omiya Park | Statement: [Omiya Bonsai Village, near, Omiya Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Omiya Park Context triple: [Omiya Bonsai Village, near, Omiya Park]
-
A.
Ōmiya Park
chosen
Ōmiya Park is a large public park in Saitama, Japan, known for its cherry blossoms, sports facilities, and the Hikawa Shrine.
-
B.
Yamashita Park
Yamashita Park is a famous seaside public park in Yokohama, Japan, known for its waterfront promenade, harbor views, and historic landmarks.
-
C.
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.
-
D.
Maizuru Park
Maizuru Park is a historic public park in Fukuoka, Japan, known for its cherry blossoms and the ruins of Fukuoka Castle.
-
E.
Nakajima Park
Nakajima Park is a large, scenic urban park in central Sapporo known for its ponds, walking paths, cultural facilities, and seasonal beauty.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733ece4488190b553a66c4b5188bc |
completed | April 9, 2026, 5:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8546b41081909e13152c4df2eb1c |
completed | April 14, 2026, 6:19 p.m. |
Created at: April 8, 2026, 9:18 p.m.